Configuring the beam line console (NEW for Release 3.2!)

DCSS uses the blu-ice's host DISPLAY variable and restricts a user's capability based on this variable and the state of the hutch door.

1. Copy the displays.txt file from the examples directory into the top 'dcss' directory.

   blctlxx:~/release-3_2/dcss > cp examples/displays.txt .

2. Edit the file and classify your machines' consoles.

The displays.txt file is read by DCSS once at start-up and enables DCSS to determine whether or not a Blu-Ice client is 'local', in the 'hutch', or at a 'remote' location. The format is list of entries, one line for each possible display that DCSS should know about. If a Blu-Ice logs in from a display that is not listed in this file, the Blu-Ice will automatically be catagorized as 'remote'.

The format of each line entry is as follows:

category hostname display [#Description]

• The category can be either 'hutch', 'local', or 'remote'.

• The hostname is the X-windows HOST envionment variable for the machine that Blu-Ice is displaying on. This field is read but not used if the display variable starts with something other than a ':'.

• The display is the X-windows DISPLAY variable for the console that Blu-Ice is displaying on. If the display starts with a ':', then the hostname is used to determine the Blu-Ice client's location.

• The line may optionally add a comment describing the location of the terminal. This comment is broadcast to all of the Blu-Ice clients, further clarifying the location of the GUI.

NOTE: This file could be added to the mysql database schema at some point.