Environment Variables to Configure DIRAC BehaviourΒΆ

There is a small number of environment variables that can be set to control the behaviour of some DIRAC components. These variables can either be set in the bashrc file of a client or server installation or set manually when desired.

DIRAC_DEBUG_DENCODE_CALLSTACK
If set, debug information for the encoding and decoding will be printed out
DIRAC_DEBUG_STOMP
If set, the stomp library will print out debug information
DIRAC_DEPRECATED_FAIL
If set, the use of functions or objects that are marked @deprecated will fail. Useful for example in continuous integration tests against future versions of DIRAC
DIRAC_GFAL_GRIDFTP_SESSION_REUSE
If set to true or yes the GRIDFT SESSION RESUSE option will be set to True, should be set on server installations. See the information in the StorageElement page.
DIRAC_USE_JSON_DECODE
Controls the transition to JSON serialization. See the information in JSON Serialization page
DIRAC_USE_JSON_ENCODE
Controls the transition to JSON serialization. See the information in JSON Serialization page
DIRAC_USE_M2CRYPTO
If anything else than true or yes (default) DIRAC will revert back to using pyGSI instead of m2crypto for handling certificates, proxies, etc.
DIRAC_M2CRYPTO_SPLIT_HANDSHAKE
If true or yes the SSL handshake is done in a new thread (default No)
DIRAC_VOMSES
Can be set to point to a folder containing VOMSES information. See Multi-VO DIRAC
DIRAC_USE_NEWTHREADPOOL
If this environment is set to true or yes, the concurrent.futures.ThreadPoolExecutor will be used.