Customizing startup of the Graphical Environment

Step 2: Editing the Xservers file

For every X server you want scologin to manage, you must add an entry to the /usr/lib/X11/scologin/Xservers file. This file should include entries for additional displays on the local machine and entries for displays on remote machines.

Entries in the Xservers file use the following format:

display_name [display_classdisplay_type [startup_command]

The various segments of the format are described below:

name of either a local X server or a remote X display using the following syntax:


hostname specifies the name of the machine to which the display is connected. If you omit hostname, the display on the current machine is assumed. :display_number specifies the number of the display you want to use. screen_number specifies the number of the screen on the display that you want to use.

defines a display class with which display_name is associated. Although display_class is optional, it is useful if you have a large collection of similar displays and want to set scologin configuration resources for groups of them. To include several X displays in the same class, use the same display_class in each Xservers entry.

indicates either a local or remote X server:

applies only to local displays, and by default is /usr/bin/X11/X. Use startup_command to specify command line options to the X server, such as the local tty you want scologin to manage.

For example, to manage a local display on /dev/tty03 that is not yet running and a display on another SCO system named scooter, include the following lines in the /usr/lib/X11/scologin/Xservers file:

   1  :0 local /usr/bin/X11/X :0 -crt /dev/tty03
   2  scooter:1 foreign

In this example, :0 on line 1 and scooter:1 on line 2 are the display_name. Also, local on line 1 and foreign on line 2 are display_type. /usr/bin/X11/X :0 -crt /dev/tty03 is the startup_command. The -crt option associates the X server with a particular console multiscreen, in this case /dev/tty03.

The scooter:1 foreign entry indicates that you want scologin to manage the second X server running on the remote machine, scooter.

Next topic: Step 3: Enabling access to the remote display
Previous topic: Step 1: Stopping existing scologin processes

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003