SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG
DONATE


YUM REPOSITORY

 
 

MAN page from Fedora 21 xorg-x11-xinit-1.3.4-2.fc21.x86_64.rpm

XINIT

Section: User Commands (1)
Updated: xinit 1.3.4
Index 

NAME

xinit - X Window System initializer 

SYNOPSIS

xinit[ [client]options... ] [--[server] [display]options... ] 

DESCRIPTION

The xinit program is used to start the X Window System server and a firstclient program on systems that are not using a display manager such asxdm(1)or in environmentsthat use multiple window systems. When this first client exits,xinit will kill the X server and then terminate.

If no specific client program is given on the command line,xinit will look for a file in the user's home directorycalled .xinitrc to run as a shell script to start up client programs.If no such file exists, xinit will use the following as a default:

       xterm -geometry +1+1 -n login -display :0

If no specific server program is given on the command line,xinit will look for a file in the user's home directorycalled .xserverrc to run as a shell script to start up the server.If no such file exists, xinit will use the following as a default:

       X :0

Note that this assumes that there is a program named X in the currentsearch path. The site administrator should, therefore, make a link to theappropriate type of server on the machine, or create a shell script thatruns xinit with the appropriate server.

Note, when using a .xserverrc script be sure to ``exec'' the real X server.Failing to do this can make the X server slow to start and exit. For example:

       exec Xdisplaytype

An important point is that programs which are run by .xinitrcshould be run in the background if they donot exit right away, so that they don't prevent other programs fromstarting up.However, the last long-lived program started (usuallya window manager or terminal emulator) should beleft in the foreground so that the script won't exit (whichindicates that the user is done and that xinit should exit).

An alternate client and/or server may be specified on thecommand line. The desired client program and its arguments should be givenas the first command line arguments to xinit. To specify a particularserver command line, append a double dash (--) to the xinit commandline (after any client and arguments) followed by the desired server command.

Both the client program name and the server program name must begin with aslash (/) or a period (.). Otherwise, they are treated as an arguments to beappended to their respective startup lines. This makes it possible toadd arguments (for example, foreground and background colors) withouthaving to retype the whole command line.

If an explicit server name is not given and the first argument following thedouble dash (--) is a colon followed by a digit, xinit will use thatnumber as the displaynumber instead of zero. All remaining arguments are appended to the servercommand line.

 

EXAMPLES

Below are several examples of how command line arguments in xinit areused.
xinit
This will start up a server named X and run the user's .xinitrc,if it exists, or else start an xterm.
xinit -- /usr/bin/Xvnc :1
This is how one could start a specific type of server on an alternate display.
xinit -geometry =80x65+10+10 -fn 8x13 -j -fg white -bg navy
This will start up a server named X, and will append the givenarguments to the default xterm command. It will ignore .xinitrc.
xinit -e widgets -- ./Xorg -l -c
This will use the command ./Xorg -l -c to start the server and willappend the arguments -e widgets to the default xterm command.
xinit /usr/ucb/rsh fasthost cpupig -display ws:1 -- :1 -a 2 -t 5
This will start a server named X on display 1 with the arguments-a 2 -t 5. It will then start a remote shell on the machinefasthost in which it will run the command cpupig, telling itto display back on the local workstation.

Below is a sample .xinitrc that starts a clock, several terminals, andleaves the window manager running as the ``last'' application. Assuming thatthe window manager has been configured properly, the userthen chooses the ``Exit'' menu item to shut down X.

xrdb -load $HOME/.Xresourcesxsetroot -solid gray &xclock -g 50x50-0+0 -bw 0 &xload -g 50x50-50+0 -bw 0 &xterm -g 80x24+0+0 &xterm -g 80x24+0-0 &twm

Sites that want to create a common startup environment could simply createa default .xinitrc that references a site-wide startup file:

#!/bin/sh. /etc/X11/xinit/site.xinitrc

Another approach is to write a script that starts xinit with a specificshell script. Such scripts are usually named x11, xstart, orstartx and are a convenient way to provide a simple interface fornovice users:

#!/bin/shxinit /etc/X11/xinit/site.xinitrc -- /usr/bin/X -br

 

ENVIRONMENT VARIABLES

DISPLAY
This variable gets set to the name of the display to which clients shouldconnect.
XINITRC
This variable specifies an init file containing shell commands to start up theinitial windows. By default, .xinitrc in the home directory will beused.
 

FILES

.xinitrc
default client script
xterm
client to run if .xinitrc does not exist
.xserverrc
default server script
X
server to run if .xserverrc does not exist
 

SEE ALSO

X(7),startx(1),Xserver(1),Xorg(1),xorg.conf(5),xterm(1) 

AUTHOR

Bob Scheifler, MIT Laboratory for Computer Science


 

Index

NAME
SYNOPSIS
DESCRIPTION
EXAMPLES
ENVIRONMENT VARIABLES
FILES
SEE ALSO
AUTHOR

This document was created byman2html,using the manual pages.