globus_gram_job_manager_configuration - The Job Manager is generally configured using the setup-globus-gram-job-manager setup script.
This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file $GLOBUS_LOCATION/etc/globus-job-manager.conf.
Configuration File Options
Create a file to store Job Manager log messages. This file will be created in the user's home directory. If the argument to this option is on-error , then the file will be removed if the job manager completes successfully. If the argument to this optionis always , the file will not be deleted by the job manager.
Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential.
Set the GLOBUS_LOCATION environment variable to the specified Globus-Location.
Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is needed.
Set the path to the directory to store job history files.
Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /home/buildd and buildd) may be used in this path. See RSL Substitions for a list of available RSL substitutions.
The Job manager will attempt to get the listed VARs from its environment and set them the same for the job's environment. For example, -extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE
Set the default scratch directory root for the job manager. Job-specific scratch directories will be created as a subdirectory of this directory. RSL substitutions (such as /home/buildd and buildd) may be used in this path. See RSL Substitions for a list of available RSL substitutions. If this option is not present in the configuration file, then the job manager will create scratch directories as subdirectories of the user's home directory.
Set the condor architecture for this job manager to be the specified ARCH. This is required when the job manager type is condor.
Set the condor operating system name for this job manager to be the specified OSNAME. This is required when the job manager type is condor.
Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution.
Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution.
Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution.
Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution.
Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution.
Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution.
Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution.
Set the range of TCP port numbers which the job manager will use. This will also be made available in the GLOBUS_TCP_PORT_RANGE environment variable and RSL substitution.
Set the path to store job manager state files (used for restarting a job manager which fails). If this is not set, then job state files will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state directory.
Set the path to the X.509 trusted certificate directory on the job execution hosts. If not present, then the trusted certificate directory used by the job manager (usually set by the Gatekeeper) will be used
Use the named module as a way to interact with the scheduler instead of polling for job status.
Store job auditing records in DIRECTORY. This directory should be sticky and group writable but not group readable. Audit records can be uploaded to a database by using the globus-gram-audit command.
Use the string VERSION-STRING as the toolkit version in audit records.
Use the single job manager per user/jobmanager type feature