Global Overrides for SBGrid sites

Administrator Software Blacklist

Site administrators can prevent the shell initialization files from configuring software on a host by creating an empty file at /programs/local/conf/disabled-hosts/<hostname>, where <hostname> is the output of the hostname -s command. This is useful for encouraging users not to run jobs on bastion hosts, file servers, etc.

Administrator Software Version Overrides

Most of the software titles installed in the SBGrid Suite have several versions available. Typically, we try to provide at least three versions of each software package, although very old or very new applications may have fewer versions.

There are two methods for site admins to configure version overrides using files placed in a /programs/local/conf/ directory.

Site-wide Version Overrides

A file named site.conf will be read when any SBGrid shell is initialized from the installation.

Per-host Version Overrides

A file named <hostname.conf>, where <hostname> is the output of the hostname -s command, will be read after the site.conf on the host matching that hostname.

Precedence

There are three files that will be examined for version overrides during shell initialization. In order from lowest to highest precedence:

• /programs/local/conf/site.conf

• /programs/local/conf/<hostname.conf>

• $HOME/.sbgrid.conf

The overrides are reported during shell initialization:

 Configuration options in effect for this shell: Variable Setting Configuration SPIDER_L 18.10 site CNS_L 1.21 machine CCP4_L 6.1.2 personal 

See this page for details on the override syntax.