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 enlisted in fname following the file
36 format 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 ge_conf(5)) specified in the files
56 enlisted 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 -cb This parameter can be used since Grid Engine version 6.2u5 in
93 combination with the command line switch -sep. In that case the
94 output of the corresponding command will contain information
95 about the added job to core binding functionality.
96 If -cb switch is not used then -sep will behave as in GE version
98 6.2u4 and below.
99 Please note that this command-line switch will be removed from
101 Grid Engine with the next major release.
102 -Dattr obj_spec fname obj_instance,...
104 <del. from object attribs>
105 Similar to -dattr (see below) but the definition of the list
106 attributes from which entries are to be deleted is contained in
107 the file named fname. As opposed to -dattr, multiple attributes
108 can be modified. Their specification has to be enlisted in fname
109 following the file format of the corresponding object (see
110 queue_conf(5) for the queue, for example).
111 Requires root/manager privileges.
112 -Mattr obj_spec fname obj_instance,...
114 <mod. object attributes>
115 Similar to -mattr (see below) but takes specifications for the
116 object attributes to be modified from file named fname. As
117 opposed to -mattr, multiple attributes can be modified. Their
118 specification has to be enlisted in fname following the file
119 format of the corresponding object (see queue_conf(5) for the
120 queue, for example).
121 Requires root/manager privileges.
122 -Mc fname <modify complex>
124 Overwrites the complex configuration by the contents of fname.
125 The argument file must comply to the format specified in com‐
126 plex(5). Requires root or manager privilege.
127 -Mcal fname <modify calendar>
129 Overwrites the calendar definition as specified in fname. The
130 argument file must comply to the format described in calen‐
131 dar_conf(5). Requires root or manager privilege.
132 -Mckpt fname <modify ckpt. environment>
134 Overwrite an existing checkpointing environment with the defini‐
135 tions in fname (see checkpoint(5)). The name attribute in fname
136 has to match an existing checkpointing environment. Requires
137 root or manager privileges.
138 -Mconf file_list <modify configurations>
140 Modify the configurations (see ge_conf(5)) specified in the
141 files enlisted in the comma separated file_list. The configura‐
142 tion is modified for the host that is identical to the file
143 name.
144 Requires root or manager privileges.
145 -Me fname <modify execution host>
147 Overwrites the execution host configuration for the specified
148 host with the contents of fname, which must comply to the format
149 defines in host_conf(5). Requires root or manager privilege.
150 -Mhgrp file <modify host group config.>
152 Allows changing of host group configuration with a single com‐
153 mand. All host group configuration entries contained in file
154 will be applied. Configuration entries not contained in file
155 will be deleted. The file format of file must comply to the for‐
156 mat specified in hostgroup(5).
157 -Mrqs fname [mrqs_name] <modify RQS configuration>
159 Same as -mrqs (see below) but instead of invoking an editor to
160 modify the RQS configuration, the file fname is considered to
161 contain a changed configuration. The name of the rule set in
162 fname must be the same as rqs_name. If rqs_name is not set, all
163 rule sets are overwritten by the rule sets in fname Refer to
164 ge_resource_quota(5) for details on the RQS configuration for‐
165 mat. Requires root or manager privilege.
166 -Mp fname <modify PE configuration>
168 Same as -mp (see below) but instead of invoking an editor to
169 modify the PE configuration the file fname is considered to con‐
170 tain a changed configuration. Refer to ge_pe(5) for details on
171 the PE configuration format. Requires root or manager privi‐
172 lege.
173 -Mprj fname <modify project config.>
175 Same as -mprj (see below) but instead of invoking an editor to
176 modify the project configuration the file fname is considered to
177 contain a changed configuration. Refer to project(5) for
178 details on the project configuration format. Requires root or
179 manager privilege.
180 -Mq fname <modify queue configuration>
182 Same as -mq (see below) but instead of invoking an editor to
183 modify the queue configuration the file fname is considered to
184 contain a changed configuration. Refer to queue_conf(5) for
185 details on the queue configuration format. Requires root or
186 manager privilege.
187 -Msconf fname <modify scheduler configuration from
189 file>
190 The current scheduler configuration (see sched_conf(5)) is over‐
191 ridden with the configuration specified in the file. Requires
192 root or manager privilege.
193 -Mstree fname <modify share tree>
195 Modifies the definition of the share tree (see share_tree(5)).
196 The modified sharetree is read from file fname. Requires root
197 or manager privileges.
198 -Mu fname <modify ACL>
200 Takes the user access list (ACL) defined in fname to overwrite
201 any existing ACL with the same name. See access_list(5) for
202 information on the ACL configuration format. Requires root or
203 manager privilege.
204 -Muser fname <modify user>
206 Modify the user defined in fname in the Grid Engine cluster. The
207 format of the user specification is described in user(5).
208 Requires root or manager privileges.
209 -Rattr obj_spec fname obj_instance,...
211 <replace object attribs>
212 Similar to -rattr (see below) but the definition of the list
213 attributes whose content is to be replace is contained in the
214 file named fname. As opposed to -rattr, multiple attributes can
215 be modified. Their specification has to be enlisted in fname
216 following the file format of the corresponding object (see
217 queue_conf(5) for the queue, for example).
218 Requires root/manager privileges.
219 -aattr obj_spec attr_name val obj_instance,...
221 <add to object attributes>
222 Allows adding specifications to a single configuration list
223 attribute in multiple instances of an object with a single com‐
224 mand. Currently supported objects are the queue, the host, the
225 host group, the parallel environment, the resource quota sets
226 and the checkpointing interface configuration being specified as
227 queue , exechost , hostgroup , pe , rqs or ckpt in obj_spec.
228 For the obj_spec queue the obj_instance can be a cluster queue
229 name, a queue domain name or a queue instance name. Find more
230 information concerning different queue names in sge_types(1).
231 Depending on the type of the obj_instance this adds to the clus‐
232 ter queues attribute sublist the cluster queues implicit default
233 configuration value or the queue domain configuration value or
234 queue instance configuration value. The queue load_thresholds
235 parameter is an example of a list attribute. With the -aattr
236 option, entries can be added to such lists, while they can be
237 deleted with -dattr, modified with -mattr, and replaced with
238 -rattr.
239 For the obj_spec rqs the obj_instance is a unique identifier for
240 a specific rule. The identifier consists of a rule-set name and
241 either the number of the rule in the list, or the name of the
242 rule, separated by a /
243 The name of the configuration attribute to be enhanced is speci‐
244 fied with attr_name followed by val as a name=value pair. The
245 comma separated list of object instances (e.g., the list of
246 queues) to which the changes have to be applied are specified at
247 the end of the command.
248 The following restriction applies: For the exechost object the
249 load_values attribute cannot be modified (see host_conf(5)).
250 Requires root or manager privileges.
251 -acal calendar_name <add calendar>
253 Adds a new calendar definition to the Grid Engine environment.
254 Calendars are used in Grid Engine for defining availability and
255 unavailability schedules of queues. The format of a calendar
256 definition is described in calendar_conf(5).
257 With the calendar name given in the option argument qconf will
259 open a temporary file and start up the text editor indicated by
260 the environment variable EDITOR (default editor is vi(1) if EDI‐
261 TOR is not set). After entering the calendar definition and
262 closing the editor the new calendar is checked and registered
263 with ge_qmaster(8). Requires root/manager privileges.
264 -ackpt ckpt_name <add ckpt. environment>
266 Adds a checkpointing environment under the name ckpt_name to the
267 list of checkpointing environments maintained by Grid Engine and
268 to be usable to submit checkpointing jobs (see checkpoint(5) for
269 details on the format of a checkpointing environment defini‐
270 tion). Qconf retrieves a default checkpointing environment con‐
271 figuration and executes vi(1) (or $EDITOR if the EDITOR environ‐
272 ment variable is set) to allow you to customize the checkpoint‐
273 ing environment configuration. Upon exit from the editor, the
274 checkpointing environment is registered with ge_qmaster(8).
275 Requires root/manager privileges.
276 -aconf host,... <add configuration>
278 Successively adds configurations (see ge_conf(5)) For the hosts
279 in the comma separated file_list. For each host, an editor
280 ($EDITOR indicated or vi(1)) is invoked and the configuration
281 for the host can be entered. The configuration is registered
282 with ge_qmaster(8) after saving the file and quitting the edi‐
283 tor.
284 Requires root or manager privileges.
285 -ae [host_template] <add execution host>
287 Adds a host to the list of Grid Engine execution hosts. If a
288 queue is configured on a host this host is automatically added
289 to the Grid Engine execution host list. Adding execution hosts
290 explicitly offers the advantage to be able to specify parameters
291 like load scale values with the registration of the execution
292 host. However, these parameters can be modified (from their
293 defaults) at any later time via the -me option described below.
294 If the host_template argument is present, qconf retrieves the
295 configuration of the specified execution host from ge_qmaster(8)
296 or a generic template otherwise. The template is then stored in
297 a file and qconf executes vi(1) (or the editor indicated by
298 $EDITOR if the EDITOR environment variable is set) to change the
299 entries in the file. The format of the execution host specifi‐
300 cation is described in host_conf(5). When the changes are saved
301 in the editor and the editor is quit the new execution host is
302 registered with ge_qmaster(8). Requires root/manager privi‐
303 leges.
304 -ah hostname,... <add administrative host>
306 Adds hosts hostname to the Grid Engine trusted host list (a host
307 must be in this list to execute administrative Grid Engine com‐
308 mands, the sole exception to this being the execution of qconf
309 on the ge_qmaster(8) node). The default Grid Engine installation
310 procedures usually add all designated execution hosts (see the
311 -ae option above) to the Grid Engine trusted host list automati‐
312 cally. Requires root or manager privileges.
313 -ahgrp group <add host group config.>
315 Adds a new host group with the name specified in group. This
316 command invokes an editor (either vi(1) or the editor indicated
317 by the EDITOR environment variable). The new host group entry
318 is registered after changing the entry and exiting the editor.
319 Requires root or manager privileges.
320 -arqs [rqs_name] <add new RQS>
322 Adds one or more Resource Quota Set (RQS) description under the
323 names rqs_name to the list of RQSs maintained by Grid Engine
324 (see ge_resource_quota(5) for details on the format of a RQS
325 definition). Qconf retrieves a default RQS configuration and
326 executes vi(1) (or $EDITOR if the EDITOR environment variable is
327 set) to allow you to customize the RQS configuration. Upon exit
328 from the editor, the RQS is registered with ge_qmaster(8).
329 Requires root or manager privileges.
330 -am user,... <add managers>
332 Adds the indicated users to the Grid Engine manager list.
333 Requires root or manager privileges.
334 -ao user,... <add operators>
336 Adds the indicated users to the Grid Engine operator list.
337 Requires root or manager privileges.
338 -ap pe_name <add new PE>
340 Adds a Parallel Environment (PE) description under the name
341 pe_name to the list of PEs maintained by Grid Engine and to be
342 usable to submit parallel jobs (see ge_pe(5) for details on the
343 format of a PE definition). Qconf retrieves a default PE con‐
344 figuration and executes vi(1) (or $EDITOR if the EDITOR environ‐
345 ment variable is set) to allow you to customize the PE configu‐
346 ration. Upon exit from the editor, the PE is registered with
347 ge_qmaster(8). Requires root/manager privileges.
348 -at thread_name <activates thread in master>
350 Activates an additional thread in the master process.
351 thread_name might be either "scheduler" or "jvm". The corre‐
352 sponding thread is only started when it is not already running.
353 There might be only one scheduler and only one jvm thread in the
354 master process at the same time.
355 -aprj <add new project>
357 Adds a project description to the list of registered projects
358 (see project(5)). Qconf retrieves a template project configura‐
359 tion and executes vi(1) (or $EDITOR if the EDITOR environment
360 variable is set) to allow you to customize the new project. Upon
361 exit from the editor, the template is registered with ge_qmas‐
362 ter(8). Requires root or manager privileges.
363 -aq [queue_name] <add new queue>
365 Qconf retrieves the default queue configuration (see
366 queue_conf(5)) and executes vi(1) (or $EDITOR if the EDITOR
367 environment variable is set) to allow you to customize the queue
368 configuration. Upon exit from the editor, the queue is regis‐
369 tered with ge_qmaster(8). A minimal configuration requires only
370 that the queue name and queue hostlist be set. Requires root or
371 manager privileges.
372 -as hostname,... <add submit hosts>
374 Add hosts hostname to the list of hosts allowed to submit Grid
375 Engine jobs and control their behavior only. Requires root or
376 manager privileges.
377 -astnode node_path=shares,... <add share tree node>
379 Adds the specified share tree node(s) to the share tree (see
380 share_tree(5)). The node_path is a hierarchical path
381 ([/]node_name[[/.]node_name...]) specifying the location of the
382 new node in the share tree. The base name of the node_path is
383 the name of the new node. The node is initialized to the number
384 of specified shares. Requires root or manager privileges.
385 -astree <add share tree>
387 Adds the definition of a share tree to the system (see
388 share_tree(5)). A template share tree is retrieved and an edi‐
389 tor (either vi(1) or the editor indicated by $EDITOR) is invoked
390 for modifying the share tree definition. Upon exiting the edi‐
391 tor, the modified data is registered with ge_qmaster(8).
392 Requires root or manager privileges.
393 -Astree fname <add share tree>
395 Adds the definition of a share tree to the system (see
396 share_tree(5)) from the file fname. Requires root or manager
397 privileges.
398 -au user,... acl_name,... <add users to ACLs>
400 Adds users to Grid Engine user access lists (ACLs). User lists
401 are used for queue usage authentication. Requires root/man‐
402 ager/operator privileges.
403 -Auser fname <add user>
405 Add the user defined in fname to the Grid Engine cluster. The
406 format of the user specification is described in user(5).
407 Requires root or manager privileges.
408 -auser <add user>
410 Adds a user to the list of registered users (see user(5)). This
411 command invokes an editor (either vi(1) or the editor indicated
412 by the EDITOR environment variable) for a template user. The new
413 user is registered after changing the entry and exiting the edi‐
414 tor. Requires root or manager privileges.
415 -clearusage <clear sharetree usage>
417 Clears all user and project usage from the sharetree. All usage
418 will be initialized back to zero.
419 -cq wc_queue_list <clean queue>
421 Cleans queue from jobs which haven't been reaped. Primarily a
422 development tool. Requires root/manager/operator privileges.
423 Find a description of wc_queue_list in sge_types(1).
424 -dattr obj_spec attr_name val obj_instance,...
426 <delete in object attribs>
427 Allows deleting specifications in a single configuration list
428 attribute in multiple instances of an object with a single com‐
429 mand. Find more information concerning obj_spec and
430 obj_instance in the description of -aattr
431 -dcal calendar_name,... <delete calendar>
433 Deletes the specified calendar definition from Grid Engine.
434 Requires root/manager privileges.
435 -dckpt ckpt_name <delete ckpt. environment>
437 Deletes the specified checkpointing environment. Requires
438 root/manager privileges.
439 -dconf host,... <delete local configuration>
441 The local configuration entries for the specified hosts are
442 deleted from the configuration list. Requires root or manager
443 privilege.
444 -de host_name,... <delete execution host>
446 Deletes hosts from the Grid Engine execution host list.
447 Requires root or manager privileges.
448 -dh host_name,... <delete administrative host>
450 Deletes hosts from the Grid Engine trusted host list. The host
451 on which ge_qmaster(8) is currently running cannot be removed
452 from the list of administrative hosts. Requires root or manager
453 privileges.
454 -dhgrp group <delete host group configuration>
456 Deletes host group configuration with the name specified in
457 group. Requires root or manager privileges.
458 -drqs rqs_name_list <delete RQS>
460 Deletes the specified resource quota sets (RQS). Requires root
461 or manager privileges.
462 -dm user[,user,...] <delete managers>
464 Deletes managers from the manager list. Requires root or man‐
465 ager privileges. It is not possible to delete the admin user or
466 the user root from the manager list.
467 -do user[,user,...] <delete operators>
469 Deletes operators from the operator list. Requires root or man‐
470 ager privileges. It is not possible to delete the admin user or
471 the user root from the operator list.
472 -dp pe_name <delete parallel environment>
474 Deletes the specified parallel environment (PE). Requires root
475 or manager privileges.
476 -dprj project,... <delete projects>
478 Deletes the specified project(s). Requires root/manager privi‐
479 leges.
480 -dq queue_name,... <delete queue>
482 Removes the specified queue(s). Active jobs will be allowed to
483 run to completion. Requires root or manager privileges.
484 -ds host_name,... <delete submit host>
486 Deletes hosts from the Grid Engine submit host list. Requires
487 root or manager privileges.
488 -dstnode node_path,... <delete share tree node>
490 Deletes the specified share tree node(s). The node_path is a
491 hierarchical path ([/]node_name[[/.]node_name...]) specifying
492 the location of the node to be deleted in the share tree.
493 Requires root or manager privileges.
494 -dstree <delete share tree>
496 Deletes the current share tree. Requires root or manager privi‐
497 leges.
498 -du user,... acl_name,... <delete users from ACL>
500 Deletes one or more users from one or more Grid Engine user
501 access lists (ACLs). Requires root/manager/operator privileges.
502 -dul acl_name,... <delete user lists>
504 Deletes one or more user lists from the system. Requires
505 root/manager/operator privileges.
506 -duser user,... <delete users>"
508 Deletes the specified user(s) from the list of registered users.
509 Requires root or manager privileges.
510 -help Prints a listing of all options.
512 -k{m|s|e[j] {host,...|all}} <shutdown Grid Engine>
514 Note: The -ks switch is deprecated, may be removed in future
515 release. Please use the -kt switch instead.
516 Used to shutdown Grid Engine components (daemons). In the form
517 -km [22mge_qmaster(8) is forced to terminate in a controlled fash‐
518 ion. In the same way the -ks switch causes termination of the
519 scheduler thread. Shutdown of running ge_execd(8) processes
520 currently registered is initiated by the -ke option. If -kej is
521 specified instead, all jobs running on the execution hosts are
522 aborted prior to termination of the corresponding ge_execd(8).
523 The comma separated host list specifies the execution hosts to
524 be addressed by the -ke and -kej option. If the keyword all is
525 specified instead of a host list, all running ge_execd(8) pro‐
526 cesses are shutdown. Job abortion, initiated by the -kej option
527 will result in dr state for all running jobs until ge_execd(8)
528 is running again.
529 Requires root or manager privileges.
530 -kt thread_name <terminate master thread>"
532 Terminates a thread in the master process. Currently it is only
533 supported to shutdown the "scheduler" and the "jvm" thread. The
534 command will only be successful if the corresponding thread is
535 running.
536 -kec {id,...|all} <kill event client>
538 Used to shutdown event clients registered at ge_qmaster(8). The
539 comma separated event client list specifies the event clients to
540 be addressed by the -kec option. If the keyword all is speci‐
541 fied instead of an event client list, all running event clients
542 except special clients like the scheduler thread are terminated.
543 Requires root or manager privilege.
544 -mattr obj_spec attr_name val obj_instance,...
546 <modify object attributes>
547 Allows changing a single configuration attribute in multiple
548 instances of an object with a single command. Find more infor‐
549 mation concerning obj_spec and obj_instance in the description
550 of -aattr
551 -mc <modify complex>
553 The complex configuration (see complex(5)) is retrieved, an edi‐
554 tor is executed (either vi(1) or the editor indicated by $EDI‐
555 TOR) and the changed complex configuration is registered with
556 ge_qmaster(8) upon exit of the editor. Requires root or manager
557 privilege.
558 -mcal calendar_name <modify calendar>
560 The specified calendar definition (see calendar_conf(5)) is
561 retrieved, an editor is executed (either vi(1) or the editor
562 indicated by $EDITOR) and the changed calendar definition is
563 registered with ge_qmaster(8) upon exit of the editor. Requires
564 root or manager privilege.
565 -mckpt ckpt_name <modify ckpt. environment>
567 Retrieves the current configuration for the specified check‐
568 pointing environment, executes an editor (either vi(1) or the
569 editor indicated by the EDITOR environment variable) and regis‐
570 ters the new configuration with the ge_qmaster(8). Refer to
571 checkpoint(5) for details on the checkpointing environment con‐
572 figuration format. Requires root or manager privilege.
573 -mconf [host,...|global] <modify configuration>
575 The configuration for the specified host is retrieved, an editor
576 is executed (either vi(1) or the editor indicated by $EDITOR)
577 and the changed configuration is registered with ge_qmaster(8)
578 upon exit of the editor. If the optional host argument is omit‐
579 ted or if the special host name global is specified, the global
580 configuration is modified. The format of the configuration is
581 described in [22mge_conf(5).
582 Requires root or manager privilege.
583 -me hostname <modify execution host>
585 Retrieves the current configuration for the specified execution
586 host, executes an editor (either vi(1) or the editor indicated
587 by the EDITOR environment variable) and registers the changed
588 configuration with ge_qmaster(8) upon exit from the editor. The
589 format of the execution host configuration is described in
590 host_conf(5). Requires root or manager privilege.
591 -mhgrp group <modify host group configuration>
593 The host group entries for the host group specified in group are
594 retrieved and an editor (either vi(1) or the editor indicated by
595 the EDITOR environment variable) is invoked for modifying the
596 host group configuration. By closing the editor, the modified
597 data is registered. The format of the host group configuration
598 is described in hostgroup(5). Requires root or manager privi‐
599 leges.
600 -mrqs [rqs_name] <modify RQS configuration>
602 Retrieves the resource quota set (RQS)configuration defined in
603 rqs_name, or if rqs_name is not given, retrieves all resource
604 quota sets, executes an editor (either vi(1) or the editor indi‐
605 cated by the EDITOR environment variable) and registers the new
606 configuration with the ge_qmaster(8). Refer to
607 ge_resource_quota(5) for details on the RQS configuration for‐
608 mat. Requires root or manager privilege.
609 -mp pe_name <modify PE configuration>
611 Retrieves the current configuration for the specified parallel
612 environment (PE), executes an editor (either vi(1) or the editor
613 indicated by the EDITOR environment variable) and registers the
614 new configuration with the ge_qmaster(8). Refer to ge_pe(5) for
615 details on the PE configuration format. Requires root or man‐
616 ager privilege.
617 -mprj project <modify project>
619 Data for the specific project is retrieved (see project(5)) and
620 an editor (either vi(1) or the editor indicated by $EDITOR) is
621 invoked for modifying the project definition. Upon exiting the
622 editor, the modified data is registered. Requires root or man‐
623 ager privileges.
624 -mq queuename <modify queue configuration>
626 Retrieves the current configuration for the specified queue,
627 executes an editor (either vi(1) or the editor indicated by the
628 EDITOR environment variable) and registers the new configuration
629 with the ge_qmaster(8). Refer to queue_conf(5) for details on
630 the queue configuration format. Requires root or manager privi‐
631 lege.
632 -msconf <modify scheduler configuration>
634 The current scheduler configuration (see sched_conf(5)) is
635 retrieved, an editor is executed (either vi(1) or the editor
636 indicated by $EDITOR) and the changed configuration is regis‐
637 tered with ge_qmaster(8) upon exit of the editor. Requires root
638 or manager privilege.
639 -mstnode node_path=shares,... <modify share tree node>
641 Modifies the specified share tree node(s) in the share tree (see
642 share_tree(5)). The node_path is a hierarchical path
643 ([/]node_name[[/.]node_name...]) specifying the location of an
644 existing node in the share tree. The node is set to the number
645 of specified shares. Requires root or manager privileges.
646 -mstree <modify share tree>
648 Modifies the definition of the share tree (see share_tree(5)).
649 The present share tree is retrieved and an editor (either vi(1)
650 or the editor indicated by $EDITOR) is invoked for modifying the
651 share tree definition. Upon exiting the editor, the modified
652 data is registered with ge_qmaster(8). Requires root or manager
653 privileges.
654 -mu acl_name <modify user access lists>
656 Retrieves the current configuration for the specified user
657 access list, executes an editor (either vi(1) or the editor
658 indicated by the EDITOR environment variable) and registers the
659 new configuration with the ge_qmaster(8). Requires root or man‐
660 ager privilege.
661 -muser user <modify user>
663 Data for the specific user is retrieved (see user(5)) and an
664 editor (either vi(1) or the editor indicated by the EDITOR envi‐
665 ronment variable) is invoked for modifying the user definition.
666 Upon exiting the editor, the modified data is registered.
667 Requires root or manager privileges.
668 -purge queue attr_nm,... obj_spec
670 <purge divergent attribute settings>
671 Delete the values of the attributes defined in attr_nm from the
672 object defined in obj_spec. Obj_spec can be "queue_instance" or
673 "queue_domain". The names of the attributes are described in
674 queue_conf(1).
675 This operation only works on a single queue instance or domain.
676 It cannot be used on a cluster queue. In the case where the
677 obj_spec is "queue@@hostgroup", the attribute values defined in
678 attr_nm which are set for the indicated hostgroup are deleted,
679 but not those which are set for the hosts contained by that
680 hostgroup. If the attr_nm is '*', all attribute values set for
681 the given queue instance or domain are deleted.
682 The main difference between -dattr and -purge is that -dattr
683 removes a value from a single list attribute, whereas -purge
684 removes one or more overriding attribute settings from a cluster
685 queue configuration. With -purge, the entire attribute is
686 deleted for the given queue instance or queue domain.
687 -rattr obj_spec attr_name val obj_instance,...
689 <replace object attributes>
690 Allows replacing a single configuration list attribute in multi‐
691 ple instances of an object with a single command. Find more
692 information concerning obj_spec and obj_instance in the descrip‐
693 tion of -aattr .
694 Requires root or manager privilege.
695 -rsstnode node_path,... <show share tree node>
697 Recursively shows the name and shares of the specified share
698 tree node(s) and the names and shares of its child nodes. (see
699 share_tree(5)). The node_path is a hierarchical path
700 ([/]node_name[[/.]node_name...]) specifying the location of a
701 node in the share tree.
702 -sc <show complexes>
704 Display the complex configuration.
705 -scal calendar_name <show calendar>
707 Display the configuration of the specified calendar.
708 -scall <show calendar list>
710 Show a list of all calendars currently defined.
711 -sckpt ckpt_name <show ckpt. environment>
713 Display the configuration of the specified checkpointing envi‐
714 ronment.
715 -sckptl <show ckpt. environment list>
717 Show a list of the names of all checkpointing environments cur‐
718 rently configured.
719 -sconf [host,...|global] <show configuration>
721 Print the global or local (host specific) configuration. If the
722 optional comma separated host list argument is omitted or the
723 special string global is given, the global configuration is dis‐
724 played. The configuration in effect on a certain host is the
725 merger of the global configuration and the host specific local
726 configuration. The format of the configuration is described in
727 ge_conf(5).
728 -sconfl <show configuration list>
730 Display a list of hosts for which configurations are available.
731 The special host name global refers to the global configuration.
732 -sds <show detached settings>
734 Displays detached settings in the cluster configuration.
735 -se hostname <show execution host>
737 Displays the definition of the specified execution host.
738 -sel <show execution hosts>
740 Displays the Grid Engine execution host list.
741 -secl <show event clients>
743 Displays the Grid Engine event client list.
744 -sep <show licensed processors>
746 Note: Deprecated, may be removed in future release.
747 Displays a list of virtual processors. This value is taken from
749 the underlying OS and it depends on underlying hardware and
750 operating system whether this value represents sockets, cores or
751 supported threads.
752 If this option is used in combination with -cb parameter then
754 two additional columns will be shown in the output for the num‐
755 ber of sockets and number of cores. Currently SGE will enlist
756 these values only if the corresponding operating system of exe‐
757 cution host is Linux under kernel >= 2.6.16, or Solaris 10.
758 Other operating systems or versions might be supported with the
759 future update releases. In case these values won't be retrieved,
760 '0' character will be displayed.
761 -sh <show administrative hosts>
763 Displays the Grid Engine administrative host list.
764 -shgrp group <show host group config.>
766 Displays the host group entries for the group specified in
767 group.
768 -shgrpl <show host group lists>
770 Displays a name list of all currently defined host groups which
771 have a valid host group configuration.
772 -shgrp_tree group <show host group tree>
774 Shows a tree like structure of host group.
775 -shgrp_resolved group <show host group hosts>
777 Shows a list of all hosts which are part of the definition of
778 host group. If the host group definition contains sub host
779 groups than also these groups are resolved and the hostnames are
780 printed.
781 -srqs [rqs_name_list] <show RQS configuration>
783 Show the definition of the resource quota sets (RQS) specified
784 by the argument.
785 -srqsl <show RQS-list>
787 Show a list of all currently defined resource quota setss
788 (RQSs).
789 -sm <show managers>
791 Displays the managers list.
792 -so <show operators>
794 Displays the operator list.
795 -sobjl obj_spec attr_name val <show object list>
797 Shows a list of all configuration objects for which val matches
798 at least one configuration value of the attributes whose name
799 matches with attr_name.
800 Obj_spec can be "queue" or "queue_domain" or "queue_instance" or
802 "exechost". Note: When "queue_domain" or "queue_instance" is
803 specified as obj_spec matching is only done with the attribute
804 overridings concerning the host group or the execution host. In
805 this case queue domain names resp. queue instances are returned.
806 Attr_name can be any of the configuration file keywords enlisted
808 in queue_conf(5) or host_conf(5). Also wildcards can be used to
809 match multiple attributes.
810 Val can be an arbitrary string or a wildcard expression.
812 -sp pe_name <show PE configuration>
814 Show the definition of the parallel environment (PE) specified
815 by the argument.
816 -spl <show PE-list>
818 Show a list of all currently defined parallel environments
819 (PEs).
820 -sprj project <show project>
822 Shows the definition of the specified project (see project(5)).
823 -sprjl <show project list>
825 Shows the list of all currently defined projects.
826 -sq wc_queue_list <show queues>
828 Displays one or multiple cluster queues or queue instances. A
829 description of wc_queue_list can be found in sge_types(1).
830 -sql <show queue list>
832 Show a list of all currently defined cluster queues.
833 -ss <show submit hosts>
835 Displays the Grid Engine submit host list.
836 -ssconf <show scheduler configuration>
838 Displays the current scheduler configuration in the format
839 explained in sched_conf(5).
840 -sstnode node_path,... <show share tree node>
842 Shows the name and shares of the specified share tree node(s)
843 (see share_tree(5)). The node_path is a hierarchical path
844 ([/]node_name[[/.]node_name...]) specifying the location of a
845 node in the share tree.
846 -sstree <show share tree>
848 Shows the definition of the share tree (see share_tree(5)).
849 -sst <show formatted share tree>
851 Shows the definition of the share tree in a tree view (see
852 share_tree(5)).
853 -sss <show scheduler status>
855 Currently displays the host on which the Grid Engine scheduler
856 is active or an error message if no scheduler is running.
857 -su acl_name <show user ACL>
859 Displays a Grid Engine user access list (ACL).
860 -sul <show user lists>
862 Displays a list of names of all currently defined Grid Engine
863 user access lists (ACLs).
864 -suser user,... <show user>
866 Shows the definition of the specified user(s) (see user(5)).
867 -suserl <show users>
869 Shows the list of all currently defined users.
870 -tsm <trigger scheduler monitoring>
872 The Grid Engine scheduler is forced by this option to print
873 trace messages of its next scheduling run to the file
874 <ge_root>/<cell>/common/schedd_runlog. The messages indicate
875 the reasons for jobs and queues not being selected in that run.
876 Requires root or manager privileges.
877 Note, that the reasons for job requirements being invalid with
879 respect to resource availability of queues are displayed using
880 the format as described for the qstat(1) -F option (see descrip‐
881 tion of Full Format in section OUTPUT FORMATS of the qstat(1)
882 manual page.
883
885 GE_ROOT Specifies the location of the Grid Engine standard con‐
886 figuration files.
887 GE_CELL If set, specifies the default Grid Engine cell. To
889 address a Grid Engine cell qconf uses (in the order of
890 precedence):
891 The name of the cell specified in the environment
893 variable GE_CELL, if it is set.
894 The name of the default cell, i.e. default.
896 GE_DEBUG_LEVEL If set, specifies that debug information should be writ‐
899 ten to stderr. In addition the level of detail in which
900 debug information is generated is defined.
901 GE_QMASTER_PORT
903 If set, specifies the tcp port on which ge_qmaster(8) is
904 expected to listen for communication requests. Most
905 installations will use a services map entry instead to
906 define that port.
907 GE_EXECD_PORT If set, specifies the tcp port on which ge_execd(8) is
909 expected to listen for communication requests. Most
910 installations will use a services map entry instead to
911 define that port.
912 SGE_SINGLE_LINE
914 If set, indicates that long lines should not be broken
915 up using backslashes. This setting is useful for
916 scripts which expect one entry per line.
917
919 Modifications to a queue configuration do not affect an active queue,
920 taking effect on next invocation of the queue (i.e., the next job).
921
923 <ge_root>/<cell>/common/act_qmaster
924 Grid Engine master host file
925
927 ge_intro(1), qstat(1), checkpoint(5), complex(5), ge_conf(5),
928 host_conf(5), ge_pe(5), queue_conf(5), ge_execd(8), ge_qmaster(8),
929 ge_resource_quota(5)
930
932 See ge_intro(1) for a full statement of rights and permissions.
933GE 6.2u5 $Date: 2009/12/02 13:47:56 $ QCONF(1)