Job Server Environment Variables
There are a number of environment variables that can be used to specify the location of resources, manage the job database, and control various aspects of job execution. Some of these environment variables provide alternate means of specifying the resource; others are the sole means of specifying a resource or of overriding a default value.
|
Variable |
Purpose |
|
|
Specify the installation directory. |
|
|
Turns on debugging related to license usage. Any nonzero integer value turns on debugging. |
|
|
Specify how long to keep trying to obtain a license. The time interval between license checkout attempts can either be doubling, or constant. To use doubling time intervals, provide an integer to specify the time in seconds, or an integer value with a time unit, such as 7200s, 120m, 2h. An attempt to obtain a license is made at intervals that double after each try, starting at 10s. The final attempt is made at the specified maximum time. To use a constant time interval between license checkout attempts, provide a colon-separated pair of a time and an integer. For example,
Default: 1 minute. |
|
|
Specify the number of times a failed subjob from a distributed job is rerun before exiting with a failure. Only supported for distributed Glide and workflow jobs. Default: 3. |
|
|
Limit the number of concurrent threads that can be used by a Schrodinger application for launching subjobs. The default is 8, which allows subjobs to be submitted back to the queue rapidly. However, if the driver nodes have few cores available, setting a smaller value can avoid temporary overloading of the node when a large batch of subjobs get submitted. Default: 8. |
|
|
Specify queue arguments for job submission to a queueing system. These arguments are also used when subjobs are submitted by a master job. Queue arguments specified with this environment variable are appended to those read from |