1QCONF(1) Grid Engine User Commands QCONF(1)
2
6 qconf - Grid Engine Queue Configuration
7
9 qconf options
10
12 qconf allows the system administrator to add, delete, and modify the
13 current Grid Engine configuration, including queue management, host
14 management, complex management and user management. qconf also allows
15 you to examine the current queue configuration for existing queues.
16 qconf allows the use of the backslash, '\', character at the end of a
18 line to indicate that the next line is a continuation of the current
19 line. When displaying settings, such as the output of one of the -s*
20 options, qconf will break up long lines (lines greater than 80 charac‐
21 ters) into smaller lines using backslash line continuation where possi‐
22 ble. Lines will only be broken up at commas or whitespace. This fea‐
23 ture can be disabled by setting the SGE_SINGLE_LINE environment vari‐
24 able.
25
27 Unless denoted otherwise, the following options and the corresponding
28 operations are available to all users with a valid account.
29 -Aattr obj_spec fname obj_instance,...
31 <add to object attributes>
32 Similar to -aattr (see below) but takes specifications for the
33 object attributes to be enhanced from file named fname. As
34 opposed to -aattr, multiple attributes can be enhanced. Their
35 specification has to be listed in fname following the file for‐
36 mat of the corresponding object (see queue_conf(5) for the
37 queue, for example).
38 Requires root/manager privileges.
39 -Acal fname <add calendar>
41 Adds a new calendar definition to the Grid Engine environment.
42 Calendars are used in Grid Engine for defining availability and
43 unavailability schedules of queues. The format of a calendar
44 definition is described in calendar_conf(5).
45 The calendar definition is taken from the file fname. Requires
47 root/ manager privileges.
48 -Ackpt fname <add ckpt. environment>
50 Add the checkpointing environment as defined in fname (see
51 checkpoint(5)) to the list of supported checkpointing environ‐
52 ments. Requires root or manager privileges.
53 -Aconf file_list <add configurations>
55 Add the configurations (see sge_conf(5)) specified in the files
56 listed in the comma separated file_list. The configuration is
57 added for the host that is identical to the file name.
58 Requires root or manager privileges.
59 -Ae fname <add execution host>
61 Add the execution host defined in fname to the Grid Engine clus‐
62 ter. The format of the execution host specification is described
63 in host_conf(5). Requires root or manager privileges.
64 -Ahgrp file <add host group config>
66 Add the host group configuration defined in file. The file for‐
67 mat of file must comply to the format specified in hostgroup(5).
68 Requires root or manager privileges.
69 -Arqs fname <add RQS configuration>
71 Add the resource quota set (RQS) defined in the file named fname
72 to the Grid Engine cluster. Requires root or manager privileges.
73 -Ap fname <add PE configuration>
75 Add the parallel environment (PE) defined in fname to the Grid
76 Engine cluster. Requires root or manager privileges.
77 -Aprj fname <add new project>
79 Adds the project description defined in fname to the list of
80 registered projects (see project(5)). Requires root or manager
81 privileges.
82 -Aq fname <add new queue>
84 Add the queue defined in fname to the Grid Engine cluster.
85 Requires root or manager privileges.
86 -Au fname <add an ACL>
88 Add the user access list (ACL) defined in fname to Grid Engine.
89 User lists are used for queue usage authentication. Requires
90 root/manager/operator privileges.
91 -Dattr obj_spec fname obj_instance,...
93 <del. from object attribs>
94 Similar to -dattr (see below) but the definition of the list
95 attributes from which entries are to be deleted is contained in
96 the file named fname. As opposed to -dattr, multiple attributes
97 can be modified. Their specification has to be listed in fname
98 following the file format of the corresponding object (see
99 queue_conf(5) for the queue, for example).
100 Requires root/manager privileges.
101 -Mattr obj_spec fname obj_instance,...
103 <mod. object attributes>
104 Similar to -mattr (see below) but takes specifications for the
105 object attributes to be modified from file named fname. As
106 opposed to -mattr, multiple attributes can be modified. Their
107 specification has to be listed in fname following the file for‐
108 mat of the corresponding object (see queue_conf(5) for the
109 queue, for example).
110 Requires root/manager privileges.
111 -Mc fname <modify complex>
113 Overwrites the complex configuration by the contents of fname.
114 The argument file must comply to the format specified in com‐
115 plex(5). Requires root or manager privilege.
116 -Mcal fname <modify calendar>
118 Overwrites the calendar definition as specified in fname. The
119 argument file must comply to the format described in calen‐
120 dar_conf(5). Requires root or manager privilege.
121 -Mckpt fname <modify ckpt. environment>
123 Overwrite an existing checkpointing environment with the defini‐
124 tions in fname (see checkpoint(5)). The name attribute in fname
125 has to match an existing checkpointing environment. Requires
126 root or manager privileges.
127 -Me fname <modify execution host>
129 Overwrites the execution host configuration for the specified
130 host with the contents of fname, which must comply to the format
131 defines in host_conf(5). Requires root or manager privilege.
132 -Mhgrp file <modify host group config.>
134 Allows changing of host group configuration with a single com‐
135 mand. All host group configuration entries contained in file
136 will be applied. Configuration entries not contained in file
137 will be deleted. The file format of file must comply to the for‐
138 mat specified in hostgroup(5).
139 -Mrqs fname [rqs_name] <modify RQS configuration>
141 Same as -mrqs (see below) but instead of invoking an editor to
142 modify the RQS configuration, the file fname is considered to
143 contain a changed configuration. The name of the rule set in
144 fname must be the same as rqs_name. If rqs_name is not set, all
145 rule sets are overwritten by the rule sets in fname Refer to
146 sge_resource_quota(5) for details on the RQS configuration for‐
147 mat. Requires root or manager privilege.
148 -Mp fname <modify PE configuration>
150 Same as -mp (see below) but instead of invoking an editor to
151 modify the PE configuration the file fname is considered to con‐
152 tain a changed configuration. Refer to sge_pe(5) for details on
153 the PE configuration format. Requires root or manager privi‐
154 lege.
155 -Mprj fname <modify project config.>
157 Same as -mprj (see below) but instead of invoking an editor to
158 modify the project configuration the file fname is considered to
159 contain a changed configuration. Refer to project(5) for
160 details on the project configuration format. Requires root or
161 manager privilege.
162 -Mq fname <modify queue configuration>
164 Same as -mq (see below) but instead of invoking an editor to
165 modify the queue configuration the file fname is considered to
166 contain a changed configuration. Refer to queue_conf(5) for
167 details on the queue configuration format. Requires root or
168 manager privilege.
169 -Mstree fname <modify share tree>
171 Modifies the definition of the share tree (see share_tree(5)).
172 The modified sharetree is read from file fname. Requires root
173 or manager privileges.
174 -Mu fname <modify ACL>
176 Takes the user access list (ACL) defined in fname to overwrite
177 any existing ACL with the same name. See access_list(5) for
178 information on the ACL configuration format. Requires root or
179 manager privilege.
180 -Muser fname <modify user>
182 Modify the user defined in fname in the Grid Engine cluster. The
183 format of the user specification is described in user(5).
184 Requires root or manager privileges.
185 -Rattr obj_spec fname obj_instance,...
187 <replace object attribs>
188 Similar to -rattr (see below) but the definition of the list
189 attributes whose content is to be replace is contained in the
190 file named fname. As opposed to -rattr, multiple attributes can
191 be modified. Their specification has to be listed in fname fol‐
192 lowing the file format of the corresponding object (see
193 queue_conf(5) for the queue, for example).
194 Requires root/manager privileges.
195 -aattr obj_spec attr_name val obj_instance,...
197 <add to object attributes>
198 Allows adding specifications to a single configuration list
199 attribute in multiple instances of an object with a single com‐
200 mand. Currently supported objects are the queue, the host, the
201 host group, the parallel environment, the resource quota sets
202 and the checkpointing interface configuration being specified as
203 queue , exechost , hostgroup , pe , rqs or ckpt in obj_spec.
204 For the obj_spec queue the obj_instance can be a cluster queue
205 name, a queue domain name or a queue instance name. Find more
206 information concerning different queue names in sge_types(1).
207 Depending on the type of the obj_instance this adds to the clus‐
208 ter queues attribute sublist the cluster queues implicit default
209 configuration value or the queue domain configuration value or
210 queue instance configuration value. The queue load_thesholds
211 parameter is an example of a list attribute. With the -aattr
212 option, entries can be added to such lists, while they can be
213 deleted with -dattr, modified with -mattr, and replaced with
214 -rattr.
215 For the obj_spec rqs the obj_instance is a unique identifier for
216 a specific rule. The identifier consists of a rule-set name and
217 either the number of the rule in the list, or the name of the
218 rule, separated by a /
219 The name of the configuration attribute to be enhanced is speci‐
220 fied with attr_name followed by val as a name=value pair. The
221 comma separated list of object instances (e.g., the list of
222 queues) to which the changes have to be applied are specified at
223 the end of the command.
224 The following restriction applies: For the exechost object the
225 load_values attribute cannot be modified (see host_conf(5)).
226 Requires root or manager privileges.
227 -acal calendar_name <add calendar>
229 Adds a new calendar definition to the Grid Engine environment.
230 Calendars are used in Grid Engine for defining availability and
231 unavailability schedules of queues. The format of a calendar
232 definition is described in calendar_conf(5).
233 With the calendar name given in the option argument qconf will
235 open a temporary file and start up the text editor indicated by
236 the environment variable EDITOR (default editor is vi(1) if EDI‐
237 TOR is not set). After entering the calendar definition and
238 closing the editor the new calendar is checked and registered
239 with sge_qmaster(8). Requires root/manager privileges.
240 -ackpt ckpt_name <add ckpt. environment>
242 Adds a checkpointing environment under the name ckpt_name to the
243 list of checkpointing environments maintained by Grid Engine and
244 to be usable to submit checkpointing jobs (see checkpoint(5) for
245 details on the format of a checkpointing environment defini‐
246 tion). qconf retrieves a default checkpointing environment con‐
247 figuration and executes vi(1) (or $EDITOR if the EDITOR environ‐
248 ment variable is set) to allow you to customize the checkpoint‐
249 ing environment configuration. Upon exit from the editor, the
250 checkpointing environment is registered with sge_qmaster(8).
251 Requires root/manager privileges.
252 -aconf host,... <add configuration>
254 Successively adds configurations (see sge_conf(5)) For the hosts
255 in the comma separated file_list. For each host, an editor
256 ($EDITOR indicated or vi(1)) is invoked and the configuration
257 for the host can be entered. The configuration is registered
258 with sge_qmaster(8) after saving the file and quitting the edi‐
259 tor.
260 Requires root or manager privileges.
261 -ae [host_template] <add execution host>
263 Adds a host to the list of Grid Engine execution hosts. If a
264 queue is configured on a host this host is automatically added
265 to the Grid Engine execution host list. Adding execution hosts
266 explicitly offers the advantage to be able to specify parameters
267 like load scale values with the registration of the execution
268 host. However, these parameters can be modified (from their
269 defaults) at any later time via the -me option described below.
270 If the host_template argument is present, qconf retrieves the
271 configuration of the specified execution host from sge_qmas‐
272 ter(8) or a generic template otherwise. The template is then
273 stored in a file and qconf executes vi(1) (or the editor indi‐
274 cated by $EDITOR if the EDITOR environment variable is set) to
275 change the entries in the file. The format of the execution
276 host specification is described in host_conf(5). When the
277 changes are saved in the editor and the editor is quit the new
278 execution host is registered with sge_qmaster(8). Requires
279 root/manager privileges.
280 -ah hostname,... <add administrative host>
282 Adds hosts hostname to the Grid Engine trusted host list (a host
283 must be in this list to execute administrative Grid Engine com‐
284 mands, the sole exception to this being the execution of qconf
285 on the sge_qmaster(8) node). The default Grid Engine installa‐
286 tion procedures usually add all designated execution hosts (see
287 the -ae option above) to the Grid Engine trusted host list auto‐
288 matically. Requires root or manager privileges.
289 -ahgrp group <add host group config.>
291 Adds a new host group with the name specified in group. This
292 command invokes an editor (either vi(1) or the editor indicated
293 by the EDITOR environment variable). The new host group entry
294 is registered after changing the entry and exiting the editor.
295 Requires root or manager privileges.
296 -arqs [rqs_name] <add new RQS>
298 Adds one or more Resource Quota Set (RQS) description under the
299 names rqs_name to the list of RQSs maintained by Grid Engine
300 (see sge_resource_quota(5) for details on the format of a RQS
301 definition). qconf retrieves a default RQS configuration and
302 executes vi(1) (or $EDITOR if the EDITOR environment variable is
303 set) to allow you to customize the RQS configuration. Upon exit
304 from the editor, the RQS is registered with sge_qmaster(8).
305 Requires root or manager privileges.
306 -am user,... <add managers>
308 Adds the indicated users to the Grid Engine manager list.
309 Requires root or manager privileges.
310 -ao user,... <add operators>
312 Adds the indicated users to the Grid Engine operator list.
313 Requires root or manager privileges.
314 -ap pe_name <add new PE>
316 Adds a Parallel Environment (PE) description under the name
317 pe_name to the list of PEs maintained by Grid Engine and to be
318 usable to submit parallel jobs (see sge_pe(5) for details on the
319 format of a PE definition). qconf retrieves a default PE con‐
320 figuration and executes vi(1) (or $EDITOR if the EDITOR environ‐
321 ment variable is set) to allow you to customize the PE configu‐
322 ration. Upon exit from the editor, the PE is registered with
323 sge_qmaster(8). Requires root/manager privileges.
324 -aprj <add new project>
326 Adds a project description to the list of registered projects
327 (see project(5)). qconf retrieves a template project configura‐
328 tion and executes vi(1) (or $EDITOR if the EDITOR environment
329 variable is set) to allow you to customize the new project. Upon
330 exit from the editor, the template is registered with sge_qmas‐
331 ter(8). Requires root or manager privileges.
332 -aq [queue_name] <add new queue>
334 qconf retrieves the default queue configuration (see
335 queue_conf(5)) and executes vi(1) (or $EDITOR if the EDITOR
336 environment variable is set) to allow you to customize the queue
337 configuration. Upon exit from the editor, the queue is regis‐
338 tered with sge_qmaster(8). A minimal configuration requires
339 only that the queue name and queue hostlist be set. Requires
340 root or manager privileges.
341 -as hostname,... <add submit hosts>
343 Add hosts hostname to the list of hosts allowed to submit Grid
344 Engine jobs and control their behavior only. Requires root or
345 manager privileges.
346 -astnode node_path=shares,... <add share tree node>
348 Adds the specified share tree node(s) to the share tree (see
349 share_tree(5)). The node_path is a hierarchical path
350 ([/]node_name[[/.]node_name...]) specifying the location of the
351 new node in the share tree. The base name of the node_path is
352 the name of the new node. The node is initialized to the number
353 of specified shares. Requires root or manager privileges.
354 -astree <add share tree>
356 Adds the definition of a share tree to the system (see
357 share_tree(5)). A template share tree is retrieved and an edi‐
358 tor (either vi(1) or the editor indicated by $EDITOR) is invoked
359 for modifying the share tree definition. Upon exiting the edi‐
360 tor, the modified data is registered with sge_qmaster(8).
361 Requires root or manager privileges.
362 -Astree fname <add share tree>
364 Adds the definition of a share tree to the system (see
365 share_tree(5)) from the file fname. Requires root or manager
366 privileges.
367 -au user,... acl_name,... <add users to ACLs>
369 Adds users to Grid Engine user access lists (ACLs). User lists
370 are used for queue usage authentication. Requires root/man‐
371 ager/operator privileges.
372 -Auser fname <add user>
374 Add the user defined in fname to the Grid Engine cluster. The
375 format of the user specification is described in user(5).
376 Requires root or manager privileges.
377 -auser <add user>
379 Adds a user to the list of registered users (see user(5)). This
380 command invokes an editor (either vi(1) or the editor indicated
381 by the EDITOR environment variable) for a template user. The new
382 user is registered after changing the entry and exiting the edi‐
383 tor. Requires root or manager privileges.
384 -clearusage <clear sharetree usage>
386 Clears all user and project usage from the sharetree. All usage
387 will be initialized back to zero.
388 -cq wc_queue_list <clean queue>
390 Cleans queue from jobs which haven't been reaped. Primarily a
391 development tool. Requires root/manager/operator privileges.
392 Find a description of wc_queue_list in sge_types(1).
393 -dattr obj_spec attr_name val obj_instance,...
395 <delete in object attribs>
396 Allows deleting specifications in a single configuration list
397 attribute in multiple instances of an object with a single com‐
398 mand. Find more information concerning obj_spec and
399 obj_instance in the description of -aattr
400 -dcal calendar_name,... <delete calendar>
402 Deletes the specified calendar definition from Grid Engine.
403 Requires root/manager privileges.
404 -dckpt ckpt_name <delete ckpt. environment>
406 Deletes the specified checkpointing environment. Requires
407 root/manager privileges.
408 -dconf host,... <delete local configuration>
410 The local configuration entries for the specified hosts are
411 deleted from the configuration list. Requires root or manager
412 privilege.
413 -de host_name,... <delete execution host>
415 Deletes hosts from the Grid Engine execution host list.
416 Requires root or manager privileges.
417 -dh host_name,... <delete administrative host>
419 Deletes hosts from the Grid Engine trusted host list. The host
420 on which sge_qmaster(8) is currently running cannot be removed
421 from the list of administrative hosts. Requires root or manager
422 privileges.
423 -drqs rqs_name_list <delete RQS>
425 Deletes the specified resource quota sets (RQS). Requires root
426 or manager privileges.
427 -dm user[,user,...] <delete managers>
429 Deletes managers from the manager list. Requires root or man‐
430 ager privileges.
431 -do user[,user,...] <delete operators>
433 Deletes operators from the operator list. Requires root or man‐
434 ager privileges.
435 -dp pe_name <delete parallel environment>
437 Deletes the specified parallel environment (PE). Requires root
438 or manager privileges.
439 -dprj project,... <delete projects>
441 Deletes the specified project(s). Requires root/manager privi‐
442 leges.
443 -dq queue_name,... <delete queue>
445 Removes the specified queue(s). Active jobs will be allowed to
446 run to completion. Requires root or manager privileges.
447 -ds host_name,... <delete submit host>
449 Deletes hosts from the Grid Engine submit host list. Requires
450 root or manager privileges.
451 -dstnode node_path,... <delete share tree node>
453 Deletes the specified share tree node(s). The node_path is a
454 hierarchical path ([/]node_name[[/.]node_name...]) specifying
455 the location of the node to be deleted in the share tree.
456 Requires root or manager privileges.
457 -dstree <delete share tree>
459 Deletes the current share tree. Requires root or manager privi‐
460 leges.
461 -du user,... acl_name,... <delete users from ACL>
463 Deletes one or more users from one or more Grid Engine user
464 access lists (ACLs). Requires root/manager/operator privileges.
465 -dul acl_name,... <delete user lists>
467 Deletes one or more user lists from the system. Requires
468 root/manager/operator privileges.
469 -duser user,... <delete users>"
471 Deletes the specified user(s) from the list of registered users.
472 Requires root or manager privileges.
473 -help Prints a listing of all options.
475 -k{m|s|e[j] {host,...|all}} <shutdown Grid Engine>
477 Used to shutdown Grid Engine components (daemons). In the form
478 -km [22msge_qmaster(8) is forced to terminate in a controlled fash‐
479 ion. In the same way the -ks switch causes termination of
480 sge_schedd(8). Shutdown of running sge_execd(8) processes cur‐
481 rently registered is initiated by the -ke option. If -kej is
482 specified instead, all jobs running on the execution hosts are
483 aborted prior to termination of the corresponding sge_execd(8).
484 The comma separated host list specifies the execution hosts to
485 be addressed by the -ke and -kej option. If the keyword all is
486 specified instead of a host list, all running sge_execd(8) pro‐
487 cesses are shutdown.
488 Requires root or manager privileges.
489 -kec {id,...|all} <kill event client>
491 Used to shutdown event clients registered at sge_qmaster(8).
492 The comma separated event client list specifies the event
493 clients to be addressed by the -kec option. If the keyword all
494 is specified instead of an event client list, all running event
495 clients except special clients like the sge_schedd(8) are termi‐
496 nated. Requires root or manager privilege.
497 -mattr obj_spec attr_name val obj_instance,...
499 <modify object attributes>
500 Allows changing a single configuration attribute in multiple
501 instances of an object with a single command. Find more infor‐
502 mation concerning obj_spec and obj_instance in the description
503 of -aattr
504 -mc <modify complex>
506 The complex configuration (see complex(5)) is retrieved, an edi‐
507 tor is executed (either vi(1) or the editor indicated by $EDI‐
508 TOR) and the changed complex configuration is registered with
509 sge_qmaster(8) upon exit of the editor. Requires root or man‐
510 ager privilege.
511 -mcal calendar_name <modify calendar>
513 The specified calendar definition (see calendar_conf(5)) is
514 retrieved, an editor is executed (either vi(1) or the editor
515 indicated by $EDITOR) and the changed calendar definition is
516 registered with sge_qmaster(8) upon exit of the editor. Requires
517 root or manager privilege.
518 -mckpt ckpt_name <modify ckpt. environment>
520 Retrieves the current configuration for the specified check‐
521 pointing environment, executes an editor (either vi(1) or the
522 editor indicated by the EDITOR environment variable) and regis‐
523 ters the new configuration with the sge_qmaster(8). Refer to
524 checkpoint(5) for details on the checkpointing environment con‐
525 figuration format. Requires root or manager privilege.
526 -mconf [host,...|global] <modify configuration>
528 The configuration for the specified host is retrieved, an editor
529 is executed (either vi(1) or the editor indicated by $EDITOR)
530 and the changed configuration is registered with sge_qmaster(8)
531 upon exit of the editor. If the optional host argument is omit‐
532 ted or if the special host name global is specified, the global
533 configuration is modified. The format of the configuration is
534 described in [22msge_conf(5).
535 Requires root or manager privilege.
536 -me hostname <modify execution host>
538 Retrieves the current configuration for the specified execution
539 host, executes an editor (either vi(1) or the editor indicated
540 by the EDITOR environment variable) and registers the changed
541 configuration with sge_qmaster(8) upon exit from the editor.
542 The format of the execution host configuration is described in
543 host_conf(5). Requires root or manager privilege.
544 -mhgrp group <modify host group configuration>
546 The host group entries for the host group specified in group are
547 retrieved and an editor (either vi(1) or the editor indicated by
548 the EDITOR environment variable) is invoked for modifying the
549 host group configuration. By closing the editor, the modified
550 data is registered. The format of the host group configuration
551 is described in hostgroup(5). Requires root or manager privi‐
552 leges.
553 -mrqs [rqs_name] <modify RQS configuration>
555 Retrieves the resource quota set (RQS)configuration defined in
556 rqs_name, or if rqs_name is not given, retrieves all resource
557 quota sets, executes an editor (either vi(1) or the editor indi‐
558 cated by the EDITOR environment variable) and registers the new
559 configuration with the sge_qmaster(8). Refer to
560 sge_resource_quota(5) for details on the RQS configuration for‐
561 mat. Requires root or manager privilege.
562 -mp pe_name <modify PE configuration>
564 Retrieves the current configuration for the specified parallel
565 environment (PE), executes an editor (either vi(1) or the editor
566 indicated by the EDITOR environment variable) and registers the
567 new configuration with the sge_qmaster(8). Refer to sge_pe(5)
568 for details on the PE configuration format. Requires root or
569 manager privilege.
570 -mprj project <modify project>
572 Data for the specific project is retrieved (see project(5)) and
573 an editor (either vi(1) or the editor indicated by $EDITOR) is
574 invoked for modifying the project definition. Upon exiting the
575 editor, the modified data is registered. Requires root or man‐
576 ager privileges.
577 -mq queuename <modify queue configuration>
579 Retrieves the current configuration for the specified queue,
580 executes an editor (either vi(1) or the editor indicated by the
581 EDITOR environment variable) and registers the new configuration
582 with the sge_qmaster(8). Refer to queue_conf(5) for details on
583 the queue configuration format. Requires root or manager privi‐
584 lege.
585 -msconf <modify scheduler configuration>
587 The current scheduler configuration (see sched_conf(5)) is
588 retrieved, an editor is executed (either vi(1) or the editor
589 indicated by $EDITOR) and the changed configuration is regis‐
590 tered with sge_qmaster(8) upon exit of the editor. Requires
591 root or manager privilege.
592 -Msconf fname <modify scheduler configuration from
594 file>
595 The current scheduler configuration (see sched_conf(5)) is over‐
596 ridden with the configuration specified in the file. Requires
597 root or manager privilege.
598 -mstnode node_path=shares,... <modify share tree node>
600 Modifies the specified share tree node(s) in the share tree (see
601 share_tree(5)). The node_path is a hierarchical path
602 ([/]node_name[[/.]node_name...]) specifying the location of an
603 existing node in the share tree. The node is set to the number
604 of specified shares. Requires root or manager privileges.
605 -mstree <modify share tree>
607 Modifies the definition of the share tree (see share_tree(5)).
608 The present share tree is retrieved and an editor (either vi(1)
609 or the editor indicated by $EDITOR) is invoked for modifying the
610 share tree definition. Upon exiting the editor, the modified
611 data is registered with sge_qmaster(8). Requires root or man‐
612 ager privileges.
613 -mu acl_name <modify user access lists>
615 Retrieves the current configuration for the specified user
616 access list, executes an editor (either vi(1) or the editor
617 indicated by the EDITOR environment variable) and registers the
618 new configuration with the sge_qmaster(8). Requires root or
619 manager privilege.
620 -muser user <modify user>
622 Data for the specific user is retrieved (see user(5)) and an
623 editor (either vi(1) or the editor indicated by the EDITOR envi‐
624 ronment variable) is invoked for modifying the user definition.
625 Upon exiting the editor, the modified data is registered.
626 Requires root or manager privileges.
627 -purge queue attr_nm,... obj_spec
629 <purge divergent attribute settings>
630 Delete the values of the attributes defined in attr_nm from the
631 object defined in obj_spec. Obj_spec can be "queue_instance" or
632 "queue_domain". The names of the attributes are described in
633 queue_conf(1).
634 This operation only works on a single queue instance or domain.
635 It cannot be used on a cluster queue. In the case where the
636 obj_spec is "queue@@hostgroup", the attribute values defined in
637 attr_nm which are set for the indicated hostgroup are deleted,
638 but not those which are set for the hosts contained by that
639 hostgroup. If the attr_nm is '*', all attribute values set for
640 the given queue instance or domain are deleted.
641 The main difference between -dattr and -purge is that -dattr
642 removes a value from a single list attribute, whereas -purge
643 removes one or more overriding attribute settings from a cluster
644 queue configuration. With -purge, the entire attribute is
645 deleted for the given queue instance or queue domain.
646 -rattr obj_spec attr_name val obj_instance,...
648 <replace object attributes>
649 Allows replacing a single configuration list attribute in multi‐
650 ple instances of an object with a single command. Find more
651 information concerning obj_spec and obj_instance in the descrip‐
652 tion of -aattr .
653 Requires root or manager privilege.
654 -rsstnode node_path,... <show share tree node>
656 Recursively shows the name and shares of the specified share
657 tree node(s) and the names and shares of its child nodes. (see
658 share_tree(5)). The node_path is a hierarchical path
659 ([/]node_name[[/.]node_name...]) specifying the location of a
660 node in the share tree.
661 -sc <show complexes>
663 Display the complex configuration.
664 -scal calendar_name <show calendar>
666 Display the configuration of the specified calendar.
667 -scall <show calendar list>
669 Show a list of all calendars currently defined.
670 -sckpt ckpt_name <show ckpt. environment>
672 Display the configuration of the specified checkpointing envi‐
673 ronment.
674 -sckptl <show ckpt. environment list>
676 Show a list of the names of all checkpointing environments cur‐
677 rently configured.
678 -sconf [host,...|global] <show configuration>
680 Print the global or local (host specific) configuration. If the
681 optional comma separated host list argument is omitted or the
682 special string global is given, the global configuration is dis‐
683 played. The configuration in effect on a certain host is the
684 merger of the global configuration and the host specific local
685 configuration. The format of the configuration is described in
686 sge_conf(5).
687 -sconfl <show configuration list>
689 Display a list of hosts for which configurations are available.
690 The special host name global refers to the global configuration.
691 -sds <show detached settings>
693 Displays detached settings in the cluster configuration.
694 -se hostname <show execution host>
696 Displays the definition of the specified execution host.
697 -sel <show execution hosts>
699 Displays the Grid Engine execution host list.
700 -secl <show event clients>
702 Displays the Grid Engine event client list.
703 -sep <show licensed processors>
705 Displays a list of number of processors which are licensed per
706 execution host and in total.
707 -sh <show administrative hosts>
709 Displays the Grid Engine administrative host list.
710 -shgrp group <show host group config.>
712 Displays the host group entries for the group specified in
713 group.
714 -shgrpl <show host group lists>
716 Displays a name list of all currently defined host groups which
717 have a valid host group configuration.
718 -shgrp_tree group <show host group tree>
720 Shows a tree like structure of host group.
721 -shgrp_resolved <show host group hosts>
723 Shows a list of all hosts which are part of the definition of
724 host group. If the host group definition contains sub host
725 groups than also these groups are resolved and the hostnames are
726 printed.
727 -srqs [rqs_name_list] <show RQS configuration>
729 Show the definition of the resource quota sets (RQS) specified
730 by the argument.
731 -srqsl <show RQS-list>
733 Show a list of all currently defined resource quota sets (RQSs).
734 -sm <show managers>
736 Displays the managers list.
737 -so <show operators>
739 Displays the operator list.
740 -sobjl obj_spec attr_name val <show object list>
742 Shows a list of all configuration objects for which value
743 matches at least one configuration value of the attributes whose
744 name matches attr_name.
745 Obj_spec can be "queue" or "queue_domain" or "queue_instance" or
747 "exechost". Note: When "queue_domain" or "queue_instance" is
748 specified as obj_spec matching is only done with the attribute
749 overridings concerning the host group or the execution host. In
750 this case queue domain names resp. queue instances are returned.
751 Attr_name can be any of the configuration file keywords listed
753 in queue_conf(5) or host_conf(5). Also wildcards can be used to
754 match multiple attributes.
755 Val can be an arbitrary string or a wildcard expression.
757 -sp pe_name <show PE configuration>
759 Show the definition of the parallel environment (PE) specified
760 by the argument.
761 -spl <show PE-list>
763 Show a list of all currently defined parallel environments
764 (PEs).
765 -sprj project <show project>
767 Shows the definition of the specified project (see project(5)).
768 -sprjl <show project list>
770 Shows the list of all currently defined projects.
771 -sq wc_queue_list <show queues>
773 Displays one or multiple cluster queues or queue instances. A
774 description of wc_queue_list can be found in sge_types(1).
775 -sql <show queue list>
777 Show a list of all currently defined cluster queues.
778 -ss <show submit hosts>
780 Displays the Grid Engine submit host list.
781 -ssconf <show scheduler configuration>
783 Displays the current scheduler configuration in the format
784 explained in sched_conf(5).
785 -sstnode node_path,... <show share tree node>
787 Shows the name and shares of the specified share tree node(s)
788 (see share_tree(5)). The node_path is a hierarchical path
789 ([/]node_name[[/.]node_name...]) specifying the location of a
790 node in the share tree.
791 -sstree <show share tree>
793 Shows the definition of the share tree (see share_tree(5)).
794 -sss <show scheduler status>
796 Currently displays the host on which the Grid Engine scheduler
797 is active or an error message if no scheduler is running.
798 -su acl_name <show user ACL>
800 Displays a Grid Engine user access list (ACL).
801 -sul <show user lists>
803 Displays a list of names of all currently defined Grid Engine
804 user access lists (ACLs).
805 -suser user,... <show user>
807 Shows the definition of the specified user(s) (see user(5)).
808 -suserl <show users>
810 Shows the list of all currently defined users.
811 -tsm <trigger scheduler monitoring>
813 The Grid Engine scheduler sge_schedd(8) is forced by this option
814 to print trace messages of its next scheduling run to the file
815 $SGE_ROOT/$SGE_CELL/common/schedd_runlog. The messages indicate
816 the reasons for jobs and queues not being selected in that run.
817 Requires root or manager privileges.
818 Note, that the reasons for job requirements being invalid with
820 respect to resource availability of queues are displayed using
821 the format as described for the qstat(1) -F option (see descrip‐
822 tion of Full Format in section OUTPUT FORMATS of the qstat(1)
823 manual page.
824
826 SGE_ROOT Specifies the location of the Grid Engine standard con‐
827 figuration files.
828 SGE_CELL If set, specifies the default Grid Engine cell. To
830 address a Grid Engine cell qconf uses (in the order of
831 precedence):
832 The name of the cell specified in the environment
834 variable SGE_CELL, if it is set.
835 The name of the default cell, i.e. default.
837 SGE_DEBUG_LEVEL
840 If set, specifies that debug information should be writ‐
841 ten to stderr. In addition the level of detail in which
842 debug information is generated is defined.
843 SGE_QMASTER_PORT
845 If set, specifies the tcp port on which sge_qmaster(8)
846 is expected to listen for communication requests. Most
847 installations will use a services map entry instead to
848 define that port.
849 SGE_EXECD_PORT If set, specifies the tcp port on which sge_execd(8) is
851 expected to listen for communication requests. Most
852 installations will use a services map entry instead to
853 define that port.
854 SGE_SINGLE_LINE
856 If set, indicates that long lines should not be broken
857 up using backslashes. This setting is useful for
858 scripts which expect one entry per line.
859
861 Modifications to a queue configuration do not affect an active queue,
862 taking effect on next invocation of the queue (i.e., the next job).
863
865 $SGE_ROOT/$SGE_CELL/common/act_qmaster
866 Grid Engine master host file
867
869 sge_intro(1), qstat(1), checkpoint(5), complex(5), sge_conf(5),
870 host_conf(5), sge_pe(5), queue_conf(5), sge_execd(8), sge_qmaster(8),
871 sge_schedd(8).
872
874 See sge_intro(1) for a full statement of rights and permissions.
875GE 6.1 $Date: 2007/07/19 08:17:15 $ QCONF(1)