Installing SBGrid Software
Using the SBGrid Environment
Support for Site Administrators
Hardware Support Notes
Getting Help
Support for Developers
SBGrid installations allow site-level software control for Administrators
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 is the output of the //hostname -s// command. This is useful for encouraging users not to run jobs on bastion hosts, file servers, etc.
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 , where is the output of the //hostname -s// command, will be read after the site.conf on the host matching that hostname.
There are three files that will be examined for version overrides during shell initialization. In order from lowest to highest precedence:
The overrides are reported during shell initialization:
Configuration options in effect for this shell:
Variable Setting Configuration
SPIDER_X 18.10 site
CNS_X 1.21 machine
CCP4_X 6.1.2 personal