<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html><head><meta name="robots" content="noindex">
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<!-- THIS FILE IS AUTOMATICALLY GENERATED FROM THE GLOBUS SOURCE CODE
DO NOT MODIFY.
-->
<title>Globus Reference Manual</title>
<link href="doxygen.css" rel="stylesheet" type="text/css">
<link href="tabs.css" rel="stylesheet" type="text/css">
</head>
<body>
<!-- Generated by Doxygen 1.7.3 -->
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li class="current"><a href="pages.html"><span>Related Pages</span></a></li>
</ul>
</div>
</div>
<div id="side-nav" class="ui-resizable side-nav-resizable">
<div id="nav-tree">
<div id="nav-tree-contents">
</div>
</div>
<div id="splitbar" style="-moz-user-select:none;"
class="ui-resizable-handle">
</div>
</div>
<script type="text/javascript">
initNavTree('globus_gram_job_manager_configuration.html','');
</script>
<div id="doc-content">
<div class="header">
<div class="headertitle">
<h1>Job Manager Configuration </h1> </div>
</div>
<div class="contents">
<div class="textblock"><p>The Job Manager is generally configured using the setup-globus-gram-job-manager setup script.</p>
<p>This section of the Job Manager manual describes all options which may be passed to the GRAM Job Manager in the configuration file <code>$GLOBUS_LOCATION/etc/globus-job-manager.conf</code>.</p>
<h2><a class="anchor" id="globus_gram_job_manager_configuration_opts"></a>
Configuration File Options</h2>
<dl class="user"><dt><b>-save-logfile always|on-error|never</b></dt><dd>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 <em>on-error</em> , then the file will be removed if the job manager completes successfully. If the argument to this optionis <em>always</em> , the file will not be deleted by the job manager.</dd></dl>
<dl class="user"><dt><b>-k</b></dt><dd>Indicate that the job manager was built with the kerberos GSSAPI instead of GSI. This disables checks for a delegated GSI credential.</dd></dl>
<dl class="user"><dt><b>-home GLOBUS_LOCATION</b></dt><dd>Set the GLOBUS_LOCATION environment variable to the specified Globus-Location.</dd></dl>
<dl class="user"><dt><b>-type JOB_MANAGER_TYPE</b></dt><dd>Set the type of scheduler interface to use for this job manager. A similarly named Perl module in the <code>$GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/</code> directory is needed.</dd></dl>
<dl class="user"><dt><b>-history PATH</b></dt><dd>Set the path to the directory to store job history files.</dd></dl>
<dl class="user"><dt><b>-cache-location PATH</b></dt><dd>Set the path for the GASS cache. This path must be unique for each user. RSL substitutions (such as /builddir and mockbuild) may be used in this path. See <a class="el" href="globus_gram_job_manager_job_execution_environment.html#globus_gram_job_manager_rsl_subs">RSL Substitions</a> for a list of available RSL substitutions.</dd></dl>
<dl class="user"><dt><b>-extra-envvars VAR1,VAR2,...</b></dt><dd>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</dd></dl>
<dl class="user"><dt><b>-scratch-dir-base PATH</b></dt><dd>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 /builddir and mockbuild) may be used in this path. See <a class="el" href="globus_gram_job_manager_job_execution_environment.html#globus_gram_job_manager_rsl_subs">RSL Substitions</a> 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.</dd></dl>
<dl class="user"><dt><b>-condor-arch ARCH</b></dt><dd>Set the condor architecture for this job manager to be the specified ARCH. This is required when the job manager type is <em>condor</em>.</dd></dl>
<dl class="user"><dt><b>-condor-os OSNAME</b></dt><dd>Set the condor operating system name for this job manager to be the specified OSNAME. This is required when the job manager type is <em>condor</em>.</dd></dl>
<dl class="user"><dt><b>-globus-gatekeeper-host HOST</b></dt><dd>Set the name of the gatekeeper host. This will be made available in the GLOBUS_GATEKEEPER_HOST RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-gatekeeper-port PORT</b></dt><dd>Set the TCP port of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_PORT RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-gatekeeper-subject SUBJECT</b></dt><dd>Set the GSI subject name of the gatekeeper. This will be made available in the GLOBUS_GATEKEEPER_SUBJECT RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-host-manufacturer MANUFACTURER</b></dt><dd>Set the manufacturer name of the host machine. This will be made available in the GLOBUS_HOST_MANUFACTURER RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-host-cputype CPUTYPE</b></dt><dd>Set the cpu type of the host machine. This will be made available in the GLOBUS_HOST_CPUTYPE RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-host-osname OSNAME</b></dt><dd>Set the operating system name of the host machine. This will be made available in the GLOBUS_HOST_OSNAME RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-host-osversion OSVERSION</b></dt><dd>Set the operating system version of the host machine. This will be made available in the GLOBUS_HOST_OSVERSION RSL substitution.</dd></dl>
<dl class="user"><dt><b>-globus-tcp-port-range RANGE</b></dt><dd>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.</dd></dl>
<dl class="user"><dt><b>-state-file-dir PATH</b></dt><dd>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 <code>$GLOBUS_LOCATION/tmp/gram_job_state</code> directory.</dd></dl>
<dl class="user"><dt><b>-x509-cert-dir PATH</b></dt><dd>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</dd></dl>
<dl class="user"><dt><b>-seg-module MODULE</b></dt><dd>Use the named module as a way to interact with the scheduler instead of polling for job status.</dd></dl>
<dl class="user"><dt><b>-audit-directory DIRECTORY</b></dt><dd>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.</dd></dl>
<dl class="user"><dt><b>-globus-toolkit-version VERSION-STRING</b></dt><dd>Use the string VERSION-STRING as the toolkit version in audit records.</dd></dl>
<dl class="user"><dt><b>-single</b></dt><dd>Use the single job manager per user/jobmanager type feature </dd></dl>
</div></div>
</div>
<div id="nav-path" class="navpath">
<ul>
<hr>
<p align="center">
<a href="http://www.globus.org/toolkit/about.html" target="_top">about globus</a> |
<a href="http://www.globus.org/toolkit/" target="_top">globus toolkit</a> |
<a href="https://dev.globus.org/wiki/Welcome/" target="_top">dev.globus</a>
<br>
<br>
Comments? <a href="mailto:webmaster@globus.org">webmaster@globus.org</a>
</body>
</html>
distrib
>
Fedora
>
13
>
i386
>
media
>
updates
>
by-pkgid
>
5bf60403bcc715f000a93231c4e3cefe
>
files
>
20
