sge_qmaster (8) - Linux Manuals
sge_qmaster: xxQS_NAMExx master control daemon
xxqs_name_sxx_qmaster - xxQS_NAMExx master control daemon
SYNOPSISxxqs_name_sxx_qmaster [ -help ]
DESCRIPTIONxxqs_name_sxx_qmaster controls the overall xxQS_NAMExx behavior in a cluster.
- Prints a listing of all options.
- Specifies the location of the xxQS_NAMExx standard configuration files.
If set, specifies the default xxQS_NAMExx cell. To address a xxQS_NAMExx
uses (in order of precedence):
The name of the cell specified in the environment
variable xxQS_NAME_Sxx_CELL, if it is set.
The name of the default cell, i.e. default.
- The name of the cell specified in the environment variable xxQS_NAME_Sxx_CELL, if it is set.
- If set, specifies that debug information should be written to stderr. In addition, the level of detail in which debug information is generated is defined by the defined value.
- If set, the qmaster will not daemonize.
- If set, specifies the tcp port on which is expected to listen for communication requests. Most installations will use a services map entry for the service "sge_qmaster" instead to define that port.
- If set, specifies the tcp port on which is expected to listen for communication requests. Most installations will use a services map entry for the service "sge_execd" instead to define that port.
- If set, specifies a delay in (integral seconds) before a scheduling run, for test purposes.
- If set, don't daemonize the program (for debugging).
If set, enable core dumps on Linux when the admin_user is not root.
Linux normally disables core dumps when the daemon has changed uid or
gid. Setting SGE_ENABLE_COREDUMP in xxqs_name_sxx_qmaster's
environment defeats that to enable core dumps for debugging if they
are otherwise allowed. This is typically not a big hazard with
xxQS_NAME_Sxx, since most information is exposed in the spool area
anyhow. Dumps will appear in the host spool directory.
On Solaris, may be used to enable such dumps.
- Path name of file to which to write the daemon process id at startup (default "qmaster.pid"). Note that this must be writable by the admin user (see
RESTRICTIONSxxqs_name_sxx_qmaster is usually started from root on the master or shadow master machines of the cluster. If started by a normal user, a master spool directory must be used to which the user has read/write access. In this case only jobs being submitted by that same user are handled correctly by the system.
<xxqs_name_sxx_root>/<cell>/common/configuration xxQS_NAMExx global configuration <xxqs_name_sxx_root>/<cell>/common/local_conf/<host> xxQS_NAMExx host specific configuration <xxqs_name_sxx_root>/<cell>/common/qmaster_args xxqs_name_sxx_qmaster argument file <xxqs_name_sxx_root>/<cell>/spool Default master spool directory
COPYRIGHTSee for a full statement of rights and permissions.