NAME
qconf - Grid Engine Queue Configuration
SYNTAX
qconf options
DESCRIPTION
Qconf allows the system administrator to add, delete, and
modify the current Grid Engine configuration, including
queue management, host management, complex management and
user management. Qconf also allows you to examine the
current queue configuration for existing queues.
OPTIONS
Unless denoted otherwise, the following options and the
corresponding operations are available to all users with a
valid account.
-Aattr obj_spec fname obj_instance,...
<add to object attributes>
Similar to -aattr (see below) but takes specifications
for the object attributes to be enhanced from file
named fname. As opposed to -aattr, multiple attributes
can be enhanced. Their specification has to be enlisted
in fname following the file format of the corresponding
object (see queue_conf(5) for the queue, for example).
Requires root/manager privileges.
-Ac complex_name fname <add complex>
Add the complex complex_name defined in fname to the
Grid Engine cluster. The format of the complex specifi-
cation is described in complex(5). Requires root or
manager privileges.
-Acal fname <add calendar>
Adds a new calendar definition to the Grid Engine
environment. Calendars are used in Grid Engine for
defining availability and unavailability schedules of
queues. The format of a calendar definition is
described in calendar_conf(5).
The calendar definition is taken from the file fname.
Requires root/ manager privileges.
-Ackpt fname <add ckpt. environment>
Add the checkpointing environment as defined in fname
(see checkpoint(5)) to the list of supported check-
pointing environments. Requires root or manager
privileges.
-Aconf file_list <add configurations>
Add the cluster configurations (see sge_conf(5))
specified in the files enlisted in the comma separated
file_list.
Requires root or manager privileges.
-Ae fname <add execution host>
Add the execution host defined in fname to the Grid
Engine cluster. The format of the execution host
specification is described in host_conf(5). Requires
root or manager privileges.
-Ap fname <add PE configuration>
Add the parallel environment (PE) defined in fname to
the Grid Engine cluster. Requires root or manager
privileges.
-Aprj fname <add new project>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Adds the project description defined in fname to the
list of registered projects (see project(5)). Requires
root or manager privileges.
-Aq fname <add new queue>
Add the queue defined in fname to the Grid Engine clus-
ter. Requires root or manager privileges.
-Au fname <add an ACL>
Add the user access list (ACL) defined in fname to Grid
Engine. User lists are used for queue usage authentica-
tion. Requires root/manager/operator privileges.
-Dattr obj_spec fname obj_instance,...
<del. from object attribs>
Similar to -dattr (see below) but the definition of the
list attributes from which entries are to be deleted is
contained in the file named fname. As opposed to
-dattr, multiple attributes can be modified. Their
specification has to be enlisted in fname following the
file format of the corresponding object (see
queue_conf(5) for the queue, for example).
Requires root/manager privileges.
-Mattr obj_spec fname obj_instance,...
<mod. object attributes>
Similar to -mattr (see below) but takes specifications
for the object attributes to be modified from file
named fname. As opposed to -mattr, multiple attributes
can be modified. Their specification has to be enlisted
in fname following the file format of the corresponding
object (see queue_conf(5) for the queue, for example).
Requires root/manager privileges.
-Mc complex_name fname <modify complex>
Overwrites the specified complex by the contents of
fname. The argument file must comply to the format
specified in complex(5). Requires root or manager
privilege.
-Mcal fname <modify calendar>
Overwrites the calendar definition as specified in
fname. The argument file must comply to the format
described in calendar_conf(5). Requires root or
manager privilege.
-Mckpt fname <modify ckpt. environment>
Overwrite an existing checkpointing environment with
the definitions in fname (see checkpoint(5)). The name
attribute in fname has to match an existing checkpoint-
ing environment. Requires root or manager privileges.
-Me fname <modify execution host>
Overwrites the execution host configuration for the
specified host with the contents of fname, which must
comply to the format defines in host_conf(5). Requires
root or manager privilege.
-Mp fname <modify PE configuration>
Same as -mp (see below) but instead of invoking an edi-
tor to modify the PE configuration the file fname is
considered to contain a changed configuration. Refer
to sge_pe(5) for details on the PE configuration for-
mat. Requires root or manager privilege.
-Mprj fname <modify project config.>
Same as -mprj (see below) but instead of invoking an
editor to modify the project configuration the file
fname is considered to contain a changed configuration.
Refer to project(5) for details on the project confi-
guration format. Requires root or manager privilege.
-Mq fname <modify queue configuration>
Same as -mq (see below) but instead of invoking an edi-
tor to modify the queue configuration the file fname is
considered to contain a changed configuration. Refer
to queue_conf(5) for details on the queue configuration
format. Requires root or manager privilege.
-Mqattr fname q_name,... <modify queue attributes>
DEPRECATED: Use -Mattr!
Allows changing of selected queue configuration attri-
butes in multiple queues with a single command. In all
queues contained in the comma separated queue name list
the queue attribute definitions contained in fname will
be applied. Queue attributes not contained in fname
will be left unchanged.
All queue attributes can be modified except for qname
and qhostname. Refer to queue_conf(5) for details on
the queue configuration format. Requires root or
manager privilege.
-Mu fname <modify ACL>
Takes the user access list (ACL) defined in fname to
overwrite any existing ACL with the same name. See
access_list(5) for information on the ACL configuration
format. Requires root or manager privilege.
-Rattr obj_spec fname obj_instance,...
<replace object attribs>
Similar to -rattr (see below) but the definition of the
list attributes whose content is to be replace is con-
tained in the file named fname. As opposed to -rattr,
multiple attributes can be modified. Their specifica-
tion has to be enlisted in fname following the file
format of the corresponding object (see queue_conf(5)
for the queue, for example).
Requires root/manager privileges.
-aattr obj_spec attr_name val obj_instance,...
<add to object attributes>
Allows adding specifications to a single configuration
list attribute in multiple instances of an object with
a single command. Currently supported objects are the
queue and the host configuration being specified as
queue or exechost in obj_spec. The queue load_thesholds
parameter is an example of a list attribute. With the
-aattr option, entries can be added to such lists,
while they can be deleted with -dattr, modified with
-mattr, and replaced with -rattr.
The name of the configuration attribute to be enhanced
is specified with attr_name followed by val as a
name=value pair. The comma separated list of object
instances (e.g., the list of queues) to which the
changes have to be applied are specified at the end of
the command.
The following restriction applies: For the exechost
object the load_values attribute cannot be modified
(see host_conf(5)).
Requires root or manager privileges.
-ac complex_name <add complex>
Adds a complex to the Grid Engine environment. Complex
entries contain one or more resources which may be
requested by jobs submitted to the system. The com-
plex(5) manual page contains detailed information about
the format of a complex definition.
When using the -ac option the complex name is given in
the command option. Qconf will then open a temporary
file and start up the text editor indicated by the
environment variable EDITOR (default editor is vi(1) if
EDITOR is not set). After entering the complex defini-
tion and closing the editor the new complex is checked
and registered with sge_qmaster(8). Requires
root/manager privileges.
-acal calendar_name <add calendar>
Adds a new calendar definition to the Grid Engine
environment. Calendars are used in Grid Engine for
defining availability and unavailability schedules of
queues. The format of a calendar definition is
described in calendar_conf(5).
With the calendar name given in the option argument
qconf will open a temporary file and start up the text
editor indicated by the environment variable EDITOR
(default editor is vi(1) if EDITOR is not set). After
entering the calendar definition and closing the editor
the new calendar is checked and registered with
sge_qmaster(8). Requires root/manager privileges.
-ackpt ckpt_name <add ckpt. environment>
Adds a checkpointing environment under the name
ckpt_name to the list of checkpointing environments
maintained by Grid Engine and to be usable to submit
checkpointing jobs (see checkpoint(5) for details on
the format of a checkpointing environment definition).
Qconf retrieves a default checkpointing environment
configuration and executes vi(1) (or $EDITOR if the
EDITOR environment variable is set) to allow you to
customize the checkpointing environment configuration.
Upon exit from the editor, the checkpointing environ-
ment is registered with sge_qmaster(8). Requires
root/manager privileges.
-aconf host,... <add configuration>
Successively adds cluster configurations (see
sge_conf(5)) For the hosts in the comma separated
file_list. For each host, an editor ($EDITOR indicated
or vi(1)) is invoked and the configuration for the host
can be entered. The configuration is registered with
sge_qmaster(8) after saving the file and quitting the
editor.
Requires root or manager privileges.
-ae [host_template] <add execution host>
Adds a host to the list of Grid Engine execution hosts.
If a queue is configured on a host this host is
automatically added to the Grid Engine execution host
list. Adding execution hosts explicitly offers the
advantage to be able to specify parameters like load
scale values with the registration of the execution
host. However, these parameters can be modified (from
their defaults) at any later time via the -me option
described below.
If the host_template argument is present, qconf
retrieves the configuration of the specified execution
host from sge_qmaster(8) or a generic template other-
wise. The template is then stored in a file and qconf
executes vi(1) (or the editor indicated by $EDITOR if
the EDITOR environment variable is set) to change the
entries in the file. The format of the execution host
specification is described in host_conf(5). When the
changes are saved in the editor and the editor is quit
the new execution host is registered with
sge_qmaster(8). Requires root/manager privileges.
-ah hostname,... <add administrative host>
Adds hosts hostname to the Grid Engine trusted host
list (a host must be in this list to execute adminis-
trative Grid Engine commands, the sole exception to
this being the execution of qconf on the sge_qmaster(8)
node). The default Grid Engine installation procedures
usually add all designated execution hosts (see the -ae
option above) to the Grid Engine trusted host list
automatically. Requires root or manager privileges.
-am user,... <add managers>
Adds the indicated users to the Grid Engine manager
list. Requires root or manager privileges.
-ao user,... <add operators>
Adds the indicated users to the Grid Engine operator
list. Requires root/manager privileges.
-ap pe_name <add new PE>
Adds a Parallel Environment (PE) description under the
name pe_name to the list of PEs maintained by Grid
Engine and to be usable to submit parallel jobs (see
sge_pe(5) for details on the format of a PE defini-
tion). Qconf retrieves a default PE configuration and
executes vi(1) (or $EDITOR if the EDITOR environment
variable is set) to allow you to customize the PE con-
figuration. Upon exit from the editor, the PE is
registered with sge_qmaster(8). Requires root/manager
privileges.
-aprj <add new project>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Adds a project description to the list of registered
projects (see project(5)). Qconf retrieves a template
project configuration and executes vi(1) (or $EDITOR if
the EDITOR environment variable is set) to allow you to
customize the new project. Upon exit from the editor,
the template is registered with sge_qmaster(8).
Requires root or manager privileges.
-aq [q_template] <add new queue>
Qconf retrieves either the default queue configuration
(see queue_conf(5)) or the configuration of the queue
q_template (if the optional argument is present) and
executes vi(1) (or $EDITOR if the EDITOR environment
variable is set) to allow you to customize the queue
configuration. Upon exit from the editor, the queue is
registered with sge_qmaster(8). A minimal configura-
tion requires only that the queue name and queue host-
name be set. Requires root or manager privileges.
-as hostname,... <add submit hosts>
Add hosts hostname to the list of hosts allowed to sub-
mit Grid Engine jobs and control their behavior only.
Requires root or manager privileges.
-astnode node_path=shares,... <add share tree node>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Adds the specified share tree node(s) to the share tree
(see share_tree(5)). The node_path is a hierarchical
path ([/]node_name[[/.]node_name...]) specifying the
location of the new node in the share tree. The base
name of the node_path is the name of the new node. The
node is initialized to the number of specified shares.
Requires root or manager privileges.
-astree <add share tree>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Adds the definition of a share tree to the system (see
share_tree(5)). A template share tree is retrieved and
an editor (either vi(1) or the editor indicated by
$EDITOR) is invoked for modifying the share tree defin-
ition. Upon exiting the editor, the modified data is
registered with sge_qmaster(8). Requires root or
manager privileges.
-au user,... acl_name,... <add users to ACLs>
Adds users to Grid Engine user access lists (ACLs).
User lists are used for queue usage authentication.
Requires root/manager/operator privileges.
-auser <add user>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Adds a user to the list of registered users (see
user(5)). This command invokes an editor (either vi(1)
or the editor indicated by the EDITOR environment vari-
able) for a template user. The new user is registered
after changing the entry and exiting the editor.
Requires root or manager privileges.
-cq queue_name,... <clean queue>
Cleans queue from jobs which haven't been reaped. Pri-
marily a development tool. Requires
root/manager/operator privileges.
-dattr obj_spec attr_name val obj_instance,...
<delete in object attribs>
Allows deleting specifications in a single configura-
tion list attribute in multiple instances of an object
with a single command. Currently supported objects are
the queue and the host configuration being specified as
queue or host in obj_spec. The queue load_thesholds
parameter is an example of a list attribute. With the
-dattr option, entries can be deleted from such lists,
while they can be added with -aattr, modified with
-mattr, and replaced with -rattr.
The name of the configuration attribute to be modified
is specified with attr_name followed by val defining
the name of the attribute list entry to be deleted. The
comma separated list of object instances (e.g., the
list of queues) to which the changes have to be applied
are specified at the end of the command.
The following restriction applies: For the host object
the load_values attribute cannot be modified (see
host_conf(5)).
Requires root or manager privileges.
-dc complex_name,... <delete complex>
Deletes complexes from Grid Engine. Requires
root/manager privileges.
-dcal calendar_name,... <delete calendar>
Deletes the specified calendar definition from Grid
Engine. Requires root/manager privileges.
-dckpt ckpt_name <delete ckpt. environment>
Deletes the specified checkpointing environment.
Requires root/manager privileges.
-dconf host,... <delete configuration>
The configuration entry for the specified hosts is
deleted from the configuration list. Requires root or
manager privilege.
-de host_name,... <delete execution host>
Deletes hosts from the Grid Engine execution host list.
Requires root/manager privileges.
-dh host_name,... <delete administrative host>
Deletes hosts from the Grid Engine trusted host list.
The host on which sge_qmaster(8) is currently running
cannot be removed from the list of administrative
hosts. Requires root/manager privileges.
-dm user[,user,...] <delete managers>
Deletes managers from the manager list. Requires
root/manager privileges.
-do user[,user,...] <delete operators>
Deletes operators from the operator list. Requires
root/manager privileges.
-dp pe_name <delete parallel environment>
Deletes the specified parallel environment (PE).
Requires root/manager privileges.
-dprj project,... <delete projects>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Deletes the specified project(s). Requires root/manager
privileges.
-dq queue_name,... <delete queue>
Removes the specified queue(s). Active jobs will be
allowed to run to completion. Requires root/manager
privileges.
-ds host_name,... <delete submit host>
Deletes hosts from the Grid Engine submit host list.
Requires root/manager privileges.
-dstnode node_path,... <delete share tree node>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Deletes the specified share tree node(s). The
node_path is a hierarchical path
([/]node_name[[/.]node_name...]) specifying the loca-
tion of the node to be deleted in the share tree.
Requires root or manager privileges.
-dstree <delete share tree>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Deletes the current share tree. Requires root or
manager privileges.
-du user,... acl_name,... <delete users from ACL>
Deletes one or more users from one or more Grid Engine
user access lists (ACLs). Requires
root/manager/operator privileges.
-dul acl_name,... <delete user lists>
Deletes one or more user lists from the system.
Requires root/manager/operator privileges.
-duser user,... <delete users>"
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Deletes the specified user(s) from the list of
registered users. Requires root or manager privileges.
-help
Prints a listing of all options.
-k{m|s|e[j] [host,...]} <shutdown Grid Engine>
Used to shutdown Grid Engine components (daemons). In
the form -km sge_qmaster(8) is forced to terminate in a
controlled fashion. In the same way the -ks switch
causes termination of sge_schedd(8). Shutdown of all
running sge_execd(8) processes currently registered is
initiated by the -ke option. If -kej is specified
instead, all jobs running on the execution hosts are
aborted prior to termination of the corresponding
sge_execd(8). The optional comma separated host list
specifies the execution hosts to be addressed by the
-ke and -kej option.
Requires root or manager privileges.
-mattr obj_spec attr_name val obj_instance,...
<modify object attributes>
Allows changing a single configuration attribute in
multiple instances of an object with a single command.
Currently supported objects are the queue and the host
configuration being specified as queue or host in
obj_spec.
Note, that "-mattr queue attr_name val q_name, ..." is
equivalent to "-mqattr attr_name val q_name,..." (see
below). The latter is available for backward compati-
bility.
The name of the configuration attribute to be modified
is specified with attr_name followed by the value to
which the attribute is going to be set. If the attri-
bute is a list, such as the queue load_thresholds, val
can be a name=value pair, in which case only a
corresponding entry in the list is changed. Refer to
the -aattr, -dattr and -rattr options for a description
of further means to change specifically such list
attributes.
The comma separated list of object instances (e.g., the
list of queues) to which the changes have to be applied
are specified at the end of the command.
The following restrictions apply: For the queue object
the qname and qhostname attributes cannot be modified
(see queue_conf(5)). For the host object the hostname,
load_values and processors attributes cannot be modi-
fied (see host_conf(5)).
Requires root or manager privilege.
-mc complex_name <modify complex>
The specified complex configuration (see complex(5)) is
retrieved, an editor is executed (either vi(1) or the
editor indicated by $EDITOR) and the changed complex
configuration is registered with sge_qmaster(8) upon
exit of the editor. Requires root or manager
privilege.
-mcal calendar_name <modify calendar>
The specified calendar definition (see
calendar_conf(5)) is retrieved, an editor is executed
(either vi(1) or the editor indicated by $EDITOR) and
the changed calendar definition is registered with
sge_qmaster(8) upon exit of the editor. Requires root
or manager privilege.
-mckpt ckpt_name <modify ckpt. environment>
Retrieves the current configuration for the specified
checkpointing environment, executes an editor (either
vi(1) or the editor indicated by the EDITOR environment
variable) and registers the new configuration with the
sge_qmaster(8). Refer to checkpoint(5) for details on
the checkpointing environment configuration format.
Requires root or manager privilege.
-mconf [host,...|global] <modify configuration>
The configuration for the specified host is retrieved,
an editor is executed (either vi(1) or the editor indi-
cated by $EDITOR) and the changed configuration is
registered with sge_qmaster(8) upon exit of the editor.
If the optional host argument is omitted or if the spe-
cial host name "global" is specified, the cell global
configuration is modified. The format of the host
configuration is described in sge_conf(5).
Requires root or manager privilege.
-me hostname <modify execution host>
Retrieves the current configuration for the specified
execution host, executes an editor (either vi(1) or the
editor indicated by the EDITOR environment variable)
and registers the changed configuration with
sge_qmaster(8) upon exit from the editor. The format
of the execution host configuration is described in
host_conf(5). Requires root or manager privilege.
-mp pe_name <modify PE configuration>
Retrieves the current configuration for the specified
parallel environment (PE), executes an editor (either
vi(1) or the editor indicated by the EDITOR environment
variable) and registers the new configuration with the
sge_qmaster(8). Refer to sge_pe(5) for details on the
PE configuration format. Requires root or manager
privilege.
-mprj project <modify project>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Data for the specific project is retrieved (see pro-
ject(5)) and an editor (either vi(1) or the editor
indicated by $EDITOR) is invoked for modifying the pro-
ject definition. Upon exiting the editor, the modified
data is registered. Requires root or manager
privileges.
-mq queuename <modify queue configuration>
Retrieves the current configuration for the specified
queue, executes an editor (either vi(1) or the editor
indicated by the EDITOR environment variable) and
registers the new configuration with the
sge_qmaster(8). Refer to queue_conf(5) for details on
the queue configuration format. Requires root or
manager privilege.
-mqattr attr_name q_name,... <modify queue attributes>
DEPRECATED: Use -mattr!
Allows changing of a single queue configuration attri-
bute in multiple queues with a single command. In all
queues contained in the comma separated queue name list
the value of the attribute attr_name will be overwrit-
ten with val.
All queue attributes can be modified except for qname
and qhostname. Refer to queue_conf(5) for details on
the queue configuration format. Requires root or
manager privilege.
-msconf <modify scheduler configuration>
The current scheduler configuration (see sched_conf(5))
is retrieved, an editor is executed (either vi(1) or
the editor indicated by $EDITOR) and the changed confi-
guration is registered with sge_qmaster(8) upon exit of
the editor. Requires root or manager privilege.
-mstnode node_path=shares,... <modify share tree node>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Modifies the specified share tree node(s) in the share
tree (see share_tree(5)). The node_path is a hierarch-
ical path ([/]node_name[[/.]node_name...]) specifying
the location of an existing node in the share tree.
The node is set to the number of specified shares.
Requires root or manager privileges.
-mstree <modify share tree>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Modifies the definition of the share tree (see
share_tree(5)). The present share tree is retrieved
and an editor (either vi(1) or the editor indicated by
$EDITOR) is invoked for modifying the share tree defin-
ition. Upon exiting the editor, the modified data is
registered with sge_qmaster(8). Requires root or
manager privileges.
-mu acl_name <modify user access lists>
Retrieves the current configuration for the specified
user access list, executes an editor (either vi(1) or
the editor indicated by the EDITOR environment vari-
able) and registers the new configuration with the
sge_qmaster(8). Requires root or manager privilege.
-rattr obj_spec attr_name val obj_instance,...
<replace object attributes>
Allows replacing a single configuration list attribute
in multiple instances of an object with a single com-
mand. Currently supported objects are the queue and the
host configuration being specified as queue or exechost
in obj_spec. The queue load_thesholds parameter is an
example of a list attribute. With the -rattr option,
such lists can be replaced, while entries can be added
to them with -aattr, deleted with -dattr, and modified
with -mattr.
The name of the configuration attribute to be modified
is specified with attr_name followed by val defining
the new setting of the attribute. The comma separated
list of object instances (e.g., the list of queues) to
which the changes have to be applied are specified at
the end of the command.
The following restriction applies: For the host object
the load_values attribute cannot be modified (see
host_conf(5)).
Requires root or manager privilege.
-muser user <modify user>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Data for the specific user is retrieved (see user(5))
and an editor (either vi(1) or the editor indicated by
the EDITOR environment variable) is invoked for modify-
ing the user definition. Upon exiting the editor, the
modified data is registered. Requires root or manager
privileges.
-sc complex_name,... <show complexes>
Display the configuration of one or more complexes.
-scal calendar_name <show calendar>
Display the configuration of the specified calendar.
-scall <show calendar list>
Show a list of all calendars currently defined.
-scl <show complex list names>
Show a list of all complexes currently configured.
-sckpt ckpt_name <show ckpt. environment>
Display the configuration of the specified checkpoint-
ing environment.
-sckptl <show ckpt. environment list>
Show a list of the names of all checkpointing environ-
ments currently configured.
-sconf [host,...|global] <show configuration>
Print the cluster configuration being in effect glo-
bally or on specified host(s). If the optional comma
separated host list argument is omitted or the special
string global is given, the global cell configuration
is displayed. For any other hostname in the list the
merger of the global configuration and the host
specific configuration is displayed. The format of
the host configuration is described in sge_conf(5).
-sconfl <show configuration list>
Display a list of hosts for which configurations are
available. The special host name "global" refers to the
cell global configuration.
-se hostname <show execution host>
Displays the definition of the specified execution
host.
-sel <show execution hosts>
Displays the Grid Engine execution host list.
-sep <show licensed processors>
Displays a list of number of processors which are
licensed per execution host and in total.
-sh <show administrative hosts>
Displays the Grid Engine administrative host list.
-sm <show managers>
Displays the managers list.
-so <show operators>
Displays the operator list.
-sp pe_name <show PE configuration>
Show the definition of the parallel environment (PE)
specified by the argument.
-spl <show PE-list>
Show a list of all currently defined parallel environ-
ments (PEs).
-sprj project <show project>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Shows the definition of the specified project (see pro-
ject(5)).
-sprjl <show project list>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Shows the list of all currently defined projects.
-sq queue_name[,queue_name,...]<show queues>
Displays one or multiple queues.
-sql <show queue list>
Show a list of all currently defined queues.
-ss <show submit hosts>
Displays the Grid Engine submit host list.
-ssconf <show scheduler configuration>
Displays the current scheduler configuration in the
format explained in sched_conf(5).
-sstnode node_path,... <show share tree node>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Shows the name and shares of the specified share tree
node(s) (see share_tree(5)). The node_path is a
hierarchical path ([/]node_name[[/.]node_name...])
specifying the location of a node in the share tree.
-sstree <show share tree>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Shows the definition of the share tree (see
share_tree(5)).
-sss <show scheduler status>
Currently displays the host on which the Grid Engine
scheduler is active or an error message if no scheduler
is running.
-su acl_name <show user ACL>
Displays a Grid Engine user access list (ACL).
-sul <show user lists>
Displays a list of names of all currently defined Grid
Engine user access lists (ACLs).
-suser user,... <show user>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Shows the definition of the specified user(s) (see
user(5)).
-suserl <show users>
This option is only supported in case of a Grid Engine
Enterprise Edition system. It is not available for Grid
Engine systems.
Shows the list of all currently defined users.
-tsm <trigger scheduler monitoring>
The Grid Engine scheduler sge_schedd(8) is forced by
this option to print trace messages of its next
scheduling run to the file
<sge_root>/<cell>/common/schedd_runlog. The messages
indicate the reasons for jobs and queues not being
selected in that run. Requires root or manager
privileges.
Note, that the reasons for job requirements being
invalid with respect to resource availability of queues
are displayed using the format as described for the
qstat(1) -F option (see description of Full Format in
section OUTPUT FORMATS of the qstat(1) manual page.
ENVIRONMENTAL VARIABLES
SGE_ROOT Specifies the location of the Grid Engine
standard configuration files.
SGE_CELL If set, specifies the default Grid Engine
cell. To address a Grid Engine cell qconf
uses (in the order of precedence):
The name of the cell specified in the
environment variable SGE_CELL, if it is
set.
The name of the default cell, i.e.
default.
SGE_DEBUG_LEVEL
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.
COMMD_PORT If set, specifies the tcp port on which
sge_commd(8) is expected to listen for com-
munication requests. Most installations will
use a services map entry instead to define
that port.
COMMD_HOST If set, specifies the host on which the par-
ticular sge_commd(8) to be used for Grid
Engine communication of the qconf client
resides. Per default the local host is used.
RESTRICTIONS
Modifications to a queue configuration do not affect an
active queue, taking effect on next invocation of the queue
(i.e., the next job).
FILES
<sge_root>/<cell>/common/act_qmaster
Grid Engine master host file
SEE ALSO
sge_intro(1), qstat(1), checkpoint(5), complex(5),
sge_conf(5), host_conf(5), sge_pe(5), queue_conf(5),
sge_execd(8), sge_qmaster(8), sge_schedd(8).
COPYRIGHT
See sge_intro(1) for a full statement of rights and permis-
sions.
Man(1) output converted with
man2html