1globus_gram_job_manager_configgluorbautsiognr(a3mg)ljoobbusm_agnraagme_rjob_manager_configuration(3)
2
3
4

NAME

6       globus_gram_job_manager_configuration - Job Manager Configuration The
7       Job Manager is generally configured using the setup-globus-gram-job-
8       manager setup script.
9
10       This section of the Job Manager manual describes all options which may
11       be passed to the GRAM Job Manager in the configuration file
12       $GLOBUS_LOCATION/etc/globus-job-manager.conf.
13

Configuration File Options

15       -save-logfile always|on-error|never
16           Create a file to store Job Manager log messages. This file will be
17           created in the user's home directory. If the argument to this
18           option is on-error , then the file will be removed if the job
19           manager completes successfully. If the argument to this optionis
20           always , the file will not be deleted by the job manager.
21
22       -k
23           Indicate that the job manager was built with the kerberos GSSAPI
24           instead of GSI. This disables checks for a delegated GSI
25           credential.
26
27       -home GLOBUS_LOCATION
28           Set the GLOBUS_LOCATION environment variable to the specified
29           Globus-Location.
30
31       -type JOB_MANAGER_TYPE
32           Set the type of scheduler interface to use for this job manager. A
33           similarly named Perl module in the
34           $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/ directory is
35           needed.
36
37       -history PATH
38           Set the path to the directory to store job history files.
39
40       -cache-location PATH
41           Set the path for the GASS cache. This path must be unique for each
42           user. RSL substitutions (such as /builddir and mockbuild) may be
43           used in this path. See RSL Substitions for a list of available RSL
44           substitutions.
45
46       -extra-envvars VAR1,VAR2,...
47           The Job manager will attempt to get the listed VARs from its
48           environment and set them the same for the job's environment. For
49           example, -extra-envvars LD_LIBRARY_PATH,GLOBUS_TCP_PORT_RANGE
50
51       -scratch-dir-base PATH
52           Set the default scratch directory root for the job manager. Job-
53           specific scratch directories will be created as a subdirectory of
54           this directory. RSL substitutions (such as /builddir and mockbuild)
55           may be used in this path. See RSL Substitions for a list of
56           available RSL substitutions. If this option is not present in the
57           configuration file, then the job manager will create scratch
58           directories as subdirectories of the user's home directory.
59
60       -condor-arch ARCH
61           Set the condor architecture for this job manager to be the
62           specified ARCH. This is required when the job manager type is
63           condor.
64
65       -condor-os OSNAME
66           Set the condor operating system name for this job manager to be the
67           specified OSNAME. This is required when the job manager type is
68           condor.
69
70       -globus-gatekeeper-host HOST
71           Set the name of the gatekeeper host. This will be made available in
72           the GLOBUS_GATEKEEPER_HOST RSL substitution.
73
74       -globus-gatekeeper-port PORT
75           Set the TCP port of the gatekeeper. This will be made available in
76           the GLOBUS_GATEKEEPER_PORT RSL substitution.
77
78       -globus-gatekeeper-subject SUBJECT
79           Set the GSI subject name of the gatekeeper. This will be made
80           available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution.
81
82       -globus-host-manufacturer MANUFACTURER
83           Set the manufacturer name of the host machine. This will be made
84           available in the GLOBUS_HOST_MANUFACTURER RSL substitution.
85
86       -globus-host-cputype CPUTYPE
87           Set the cpu type of the host machine. This will be made available
88           in the GLOBUS_HOST_CPUTYPE RSL substitution.
89
90       -globus-host-osname OSNAME
91           Set the operating system name of the host machine. This will be
92           made available in the GLOBUS_HOST_OSNAME RSL substitution.
93
94       -globus-host-osversion OSVERSION
95           Set the operating system version of the host machine. This will be
96           made available in the GLOBUS_HOST_OSVERSION RSL substitution.
97
98       -globus-tcp-port-range RANGE
99           Set the range of TCP port numbers which the job manager will use.
100           This will also be made available in the GLOBUS_TCP_PORT_RANGE
101           environment variable and RSL substitution.
102
103       -state-file-dir PATH
104           Set the path to store job manager state files (used for restarting
105           a job manager which fails). If this is not set, then job state
106           files will be stored in the $GLOBUS_LOCATION/tmp/gram_job_state
107           directory.
108
109       -x509-cert-dir PATH
110           Set the path to the X.509 trusted certificate directory on the job
111           execution hosts. If not present, then the trusted certificate
112           directory used by the job manager (usually set by the Gatekeeper)
113           will be used
114
115       -seg-module MODULE
116           Use the named module as a way to interact with the scheduler
117           instead of polling for job status.
118
119       -audit-directory DIRECTORY
120           Store job auditing records in DIRECTORY. This directory should be
121           sticky and group writable but not group readable. Audit records can
122           be uploaded to a database by using the globus-gram-audit command.
123
124       -globus-toolkit-version VERSION-STRING
125           Use the string VERSION-STRING as the toolkit version in audit
126           records.
127
128       -single
129           Use the single job manager per user/jobmanager type feature
130
131Version 10.70                   Tue Jungl7ob2u0s1_1gram_job_manager_configuration(3)