2
.\"___INFO__MARK_BEGIN__
4
.\" Copyright: 2004 by Sun Microsystems, Inc.
7
.\" $RCSfile$ Last Update: $Date$ Revision: $Revision$
10
.\" Some handy macro definitions [from Tom Christensen's man(1) manual page].
12
.de SB \" small and bold
13
.if !"\\$1"" \\s-2\\fB\&\\$1\\s0\\fR\\$2 \\$3 \\$4 \\$5
16
.de T \" switch to typewriter font
17
.ft CW \" probably want CW if you don't have TA font
20
.de TY \" put $1 in typewriter font
29
.de M \" man page reference
30
\\fI\\$1\\fR\\|(\\$2)\\$3
32
.TH xxQS_NAME_Sxx_CONF 5 "$Date$" "xxRELxx" "xxQS_NAMExx File Formats"
35
xxqs_name_sxx_conf \- xxQS_NAMExx configuration files
40
defines the global and local xxQS_NAMExx configurations and can be
43
using the \-sconf/\-mconf options. Only root or the cluster administrator may
45
.I xxqs_name_sxx_conf.
47
At its initial start-up,
48
.M xxqs_name_sxx_qmaster 8
49
checks to see if a valid xxQS_NAMExx configuration is available at a
50
well known location in the xxQS_NAMExx internal directory hierarchy.
51
If so, it loads that configuration information and proceeds.
53
.M xxqs_name_sxx_qmaster 8
54
writes a generic configuration containing default values to that same
56
The xxQS_NAMExx execution daemons
57
.M xxqs_name_sxx_execd 8
58
upon start-up retrieve their configuration from
59
.M xxqs_name_sxx_qmaster 8 .
61
The actual configuration for both
62
.M xxqs_name_sxx_qmaster 8
64
.M xxqs_name_sxx_execd 8
65
is a superposition of a \fIglobal\fP configuration and
66
a \fIlocal\fP configuration pertinent for the host on which
67
a master or execution daemon resides.
68
If a local configuration is available, its entries overwrite the
69
corresponding entries of the global configuration. \fBNote:\fP The local
70
configuration does not have to contain all valid configuration entries,
71
but only those which need to be modified against the global entries.
73
Note: xxQS_NAMExx allows backslashes (\\) be used to escape newline
74
(\\newline) characters. The backslash and the newline are replaced with a
75
space (" ") character before any interpretation.
80
The paragraphs that follow provide brief descriptions of the individual
81
parameters that compose the global and local configurations for a
85
.SS "\fBexecd_spool_dir\fP"
86
The execution daemon spool directory path. Again, a feasible spool
87
directory requires read/write access permission for root. The entry in
88
the global configuration for this parameter can be overwritten by
89
execution host local configurations, i.e. each
90
.M xxqs_name_sxx_execd 8
91
may have a private spool directory with a different path, in which case
92
it needs to provide read/write permission for the root account of the
93
corresponding execution host only.
95
Under \fBexecd_spool_dir\fP a directory named corresponding
96
to the unqualified hostname of the execution host is opened and
97
contains all information spooled to disk. Thus, it is possible for the
98
\fBexecd_spool_dir\fPs of all execution hosts to physically reference the
100
(the root access restrictions mentioned above need to be met, however).
102
Changing the global \fBexecd_spool_dir\fP
103
parameter set at installation time is not supported
104
in a running system. If the change should still be done
105
it is required to restart all affected execution daemons. Please make sure running
106
jobs have finished before doing so,
107
otherwise running jobs will be lost.
110
The default location for the execution daemon spool
111
directory is $xxQS_NAME_Sxx_ROOT/$xxQS_NAME_Sxx_CELL/spool.
113
The global configuration entry for this value
114
may be overwritten by the execution host local configuration.
118
\fBmailer\fP is the absolute pathname to the electronic mail delivery
119
agent on your system. It must accept the following syntax:
122
mailer -s <subject-of-mail-message> <recipient>
126
.M xxqs_name_sxx_execd 8
127
may use a private mail agent. Changing \fBmailer\fP will take
130
The default for \fBmailer\fP depends on the operating system of
131
the host on which the xxQS_NAMExx master installation was run. Common
132
values are /bin/mail or /usr/bin/Mail.
134
The global configuration entry for this value
135
may be overwritten by the execution host local configuration.
140
is the absolute pathname to the X Window System terminal emulator,
144
.M xxqs_name_sxx_execd 8
145
may use a private mail agent. Changing \fBxterm\fP will take
148
The default for \fBxterm\fP is /usr/bin/X11/xterm.
150
The global configuration entry for this value
151
may be overwritten by the execution host local configuration.
154
.SS "\fBload_sensor\fP"
155
A comma separated list of executable shell script paths or programs
157
.M xxqs_name_sxx_execd 8
158
and to be used in order to retrieve site configurable load information
159
(e.g. free space on a certain disk partition).
162
.M xxqs_name_sxx_execd 8
163
may use a set of private
165
programs or scripts. Changing
167
will take effect after two load report intervals (see
168
\fBload_report_time\fB). A load sensor will be restarted automatically if
169
the file modification time of the load sensor executable changes.
171
The global configuration entry for this value
172
may be overwritten by the execution host local configuration.
174
In addition to the load sensors configured via
176
.M xxqs_name_sxx_exec 8
177
searches for an executable file named
179
in the execution host's xxQS_NAMExx binary directory path.
180
If such a file is found, it is treated like the configurable load sensors
181
defined in \fBload_sensor\fP. This facility is intended for pre-installing
182
a default load sensor.
186
The executable path of a shell script that is started before execution
187
of xxQS_NAMExx jobs with the same environment setting as that for the
189
jobs to be started afterwards.
190
An optional prefix "user@" specifies the user under which this procedure
191
is to be started. The procedures standard
192
output and the error output stream are written to the same file used also for
193
the standard output and error output of each job.
194
This procedure is intended as a means
195
for the xxQS_NAMExx administrator to automate the execution of general site
196
specific tasks like the preparation of temporary file systems with the
197
need for the same context information as the job.
199
.M xxqs_name_sxx_execd 8
200
may use a private prolog script.
201
Correspondingly, the execution host local
202
configurations is can be overwritten by the queue configuration (see
205
Changing \fBprolog\fP will take
208
The default for \fBprolog\fP is the special value NONE, which prevents
209
from execution of a prolog script.
211
The following special
212
variables expanded at runtime can be used (besides any other
213
strings which have to be interpreted by the procedure) to constitute
216
The name of the host on which the prolog or epilog procedures are
218
.IP "\fI$job_owner\fP"
219
The user name of the job owner.
221
xxQS_NAMExx's unique job identification number.
222
.IP "\fI$job_name\fP"
224
.IP "\fI$processors\fP"
225
The \fBprocessors\fP string as contained in the queue configuration
228
of the master queue (the queue in which the prolog and epilog procedures
231
The cluster queue name of the master queue instance, i.e. the cluster
232
queue in which the prolog and epilog procedures are started.
233
.IP "\fI$stdin_path\fP"
234
The pathname of the stdin file. This is always /dev/null for prolog,
235
pe_start, pe_stop and epilog. It is the pathname of the
236
stdin file for the job in the job script. When delegated file staging is enabled,
238
to $fs_stdin_tmp_path. When delegated file staging is not enabled, it is the stdin
239
pathname given via DRMAA or qsub.
240
.IP "\fI$stdout_path\fP"
241
.IP "\fI$stderr_path\fP"
242
The pathname of the stdout/stderr file. This always points to the
243
output/error file. When delegated file staging is enabled, this path is set to
244
$fs_stdout_tmp_path/$fs_stderr_tmp_path. When delegated file staging is not
245
enabled, it is the stdout/stderr pathname given via DRMAA or qsub.
246
.IP "\fI$merge_stderr\fP"
247
If merging of stderr and stdout is requested, this flag is "1", otherwise it is "0".
248
If this flag is 1, stdout and stderr are merged in one file, the stdout file.
249
Merging of stderr and stdout can be requested via the DRMAA job template attribute 'drmaa_join_files' (see
250
.M drmaa_attributes 3
251
) or the qsub parameter '-j y' (see
254
.IP "\fI$fs_stdin_host\fP"
255
When delegated file staging is requested for the stdin file, this is the name of
256
the host where the stdin file has to be copied from before the job is started.
257
.IP "\fI$fs_stdout_host\fP"
258
.IP "\fI$fs_stderr_host\fP"
259
When delegated file staging is requested for the stdout/stderr file, this is the
260
name of the host where the stdout/stderr file has to be copied to after the job has run.
261
.IP "\fI$fs_stdin_path\fP"
262
When delegated file staging is requested for the stdin file, this is the pathname
263
of the stdin file on the host $fs_stdin_host.
264
.IP "\fI$fs_stdout_path\fP"
265
.IP "\fI$fs_stderr_path\fP"
266
When delegated file staging is requested for the stdout/stderr file, this is the
267
pathname of the stdout/stderr file on the host $fs_stdout_host/$fs_stderr_host.
268
.IP "\fI$fs_stdin_tmp_path\fP"
269
When delegated file staging is requested for the stdin file, this is the destination
270
pathname of the stdin file on the execution host. The prolog script must copy the
271
stdin file from $fs_stdin_host:$fs_stdin_path to localhost:$fs_stdin_tmp_path to
272
establish delegated file staging of the stdin file.
273
.IP "\fI$fs_stdout_tmp_path\fP"
274
.IP "\fI$fs_stderr_tmp_path\fP"
275
When delegated file staging is requested for the stdout/stderr file, this is the
276
source pathname of the stdout/stderr file on the execution host. The epilog script
277
must copy the stdout file from localhost:$fs_stdout_tmp_path to
278
$fs_stdout_host:$fs_stdout_path (the stderr file from localhost:$fs_stderr_tmp_path
279
to $fs_stderr_host:$fs_stderr_path) to establish delegated file staging of the
281
.IP "\fI$fs_stdin_file_staging\fP"
282
.IP "\fI$fs_stdout_file_staging\fP"
283
.IP "\fI$fs_stderr_file_staging\fP"
284
When delegated file staging is requested for the stdin/stdout/stderr file, the flag
285
is set to "1", otherwise it is set to "0" (see in \fBdelegated_file_staging\fP how
286
to enable delegated file staging).
288
These three flags correspond to the DRMAA job template attribute 'drmaa_transfer_files' (see
289
.M drmaa_attributes 3
292
The global configuration entry for this value
293
may be overwritten by the execution host local configuration.
295
Exit codes for the prolog attribute can be interpreted based on the
296
following exit values:
302
100: Put job in error state
304
Anything else: Put queue in error state
309
The executable path of a shell script that is started after execution
310
of xxQS_NAMExx jobs with the same environment setting as that for the
312
jobs that has just completed. An optional prefix "user@" specifies the
313
user under which this procedure is to be started. The procedures standard
314
output and the error output stream are written to the same file used also for
315
the standard output and error output of each job.
316
This procedure is intended as a means
317
for the xxQS_NAMExx administrator to automate the execution of general site
318
specific tasks like the cleaning up of temporary file systems with the
319
need for the same context information as the job.
321
.M xxqs_name_sxx_execd 8
322
may use a private epilog script.
323
Correspondingly, the execution host local
324
configurations is can be overwritten by the queue configuration (see
327
Changing \fBepilog\fP will take
330
The default for \fBepilog\fP is the special value NONE, which prevents
331
from execution of a epilog script.
332
The same special variables as for \fBprolog\fP can be
333
used to constitute a command line.
335
The global configuration entry for this value
336
may be overwritten by the execution host local configuration.
338
Exit codes for the epilog attribute can be interpreted based on the
339
following exit values:
345
100: Put job in error state
347
Anything else: Put queue in error state
351
.SS "\fBshell_start_mode\fP"
352
This parameter defines the mechanisms which are used to actually
353
invoke the job scripts on the execution hosts. The following
354
values are recognized:
355
.IP \fIunix_behavior\fP
356
If a user starts a job shell script under UNIX interactively by
357
invoking it just with the script name the operating system's executable
358
loader uses the information provided in a comment such as `#!/bin/csh' in
359
the first line of the script to detect which command interpreter to
360
start to interpret the script. This mechanism is used by xxQS_NAMExx when
361
starting jobs if \fIunix_behavior\fP is defined as \fBshell_start_mode\fP.
363
.IP \fIposix_compliant\fP
364
POSIX does not consider first script line comments such a `#!/bin/csh'
365
as significant. The POSIX standard for batch queuing systems
366
(P1003.2d) therefore requires a compliant queuing system to ignore
367
such lines but to use user specified or configured default command
368
interpreters instead. Thus, if \fBshell_start_mode\fP is set to
369
\fIposix_compliant\fP xxQS_NAMExx will either use the command interpreter
370
indicated by the \fB\-S\fP option of the
372
command or the \fBshell\fP parameter of the queue to be used (see
376
.IP \fIscript_from_stdin\fP
377
Setting the \fBshell_start_mode\fP parameter either to \fIposix_compliant\fP
378
or \fIunix_behavior\fP requires you to set the umask in use for
379
.M xxqs_name_sxx_execd 8
380
such that every user has read access to the active_jobs directory in the
381
spool directory of the corresponding execution daemon. In case you have
382
\fBprolog\fP and \fBepilog\fP scripts configured, they also need to be
383
readable by any user who may execute jobs.
385
If this violates your
386
site's security policies you may want to set \fBshell_start_mode\fP
387
to \fIscript_from_stdin\fP. This will force xxQS_NAMExx to open the
388
job script as well as the epilog and prolog scripts for reading into
390
.M xxqs_name_sxx_execd 8
391
was started as root) before changing to the job owner's user account.
392
The script is then fed into the STDIN stream of the command interpreter
393
indicated by the \fB\-S\fP option of the
395
command or the \fBshell\fP parameter of the queue to be used (see
399
Thus setting \fBshell_start_mode\fP to \fIscript_from_stdin\fP also
400
implies \fIposix_compliant\fP behavior. \fBNote\fP, however, that
401
feeding scripts into the STDIN stream of a command interpreter may
402
cause trouble if commands like
404
are invoked inside a job script as they also process the STDIN
405
stream of the command interpreter. These problems can usually be
406
resolved by redirecting the STDIN channel of those commands to come
407
from /dev/null (e.g. rsh host date < /dev/null). \fBNote also\fP, that any
408
command-line options associated with the job are passed to the executing
409
shell. The shell will only forward them to the job if they are not
410
recognized as valid shell options.
412
Changes to \fBshell_start_mode\fP will take immediate effect.
413
The default for \fBshell_start_mode\fP is \fIposix_compliant\fP.
415
This value is a global configuration parameter only. It cannot be
416
overwritten by the execution host local configuration.
419
.SS "\fBlogin_shells\fP"
420
UNIX command interpreters like the Bourne-Shell (see
424
can be used by xxQS_NAMExx to start job scripts. The command interpreters
425
can either be started as login-shells (i.e. all system and user default
426
resource files like .login or .profile will be executed when the
427
command interpreter is started and the environment for the job will be
428
set up as if the user has just logged in) or just for command execution
429
(i.e. only shell specific resource files like .cshrc will be executed
430
and a minimal default environment is set up by xxQS_NAMExx \- see
432
The parameter \fBlogin_shells\fP contains a comma separated list of the
433
executable names of the command interpreters to be started as login-shells.
434
Shells in this list are only started as login shells if the parameter
435
\fBshell_start_mode\fP (see above) is set to \fIposix_compliant\fP.
437
Changes to \fBlogin_shells\fP will take immediate effect.
438
The default for \fBlogin_shells\fP is sh,csh,tcsh,ksh.
440
This value is a global configuration parameter only. It cannot be
441
overwritten by the execution host local configuration.
445
\fBmin_uid\fP places a lower bound on user IDs that may use the cluster. Users
446
whose user ID (as returned by
448
is less than \fBmin_uid\fP will not be allowed to run jobs on the cluster.
450
Changes to \fBmin_uid\fP will take immediate effect.
451
The default for \fBmin_uid\fP is 0.
453
This value is a global configuration parameter only. It cannot be
454
overwritten by the execution host local configuration.
458
This parameter sets the lower bound on group IDs that may use the cluster.
459
Users whose default group ID (as returned by
461
is less than \fBmin_gid\fP will not be allowed to run jobs on the cluster.
463
Changes to \fBmin_gid\fP will take immediate effect.
464
The default for \fBmin_gid\fP is 0.
466
This value is a global configuration parameter only. It cannot be
467
overwritten by the execution host local configuration.
470
.SS "\fBuser_lists \fP"
471
The \fBuser_lists\fP parameter contains a comma separated list of
472
user access lists as described in
474
Each user contained in at least one of the enlisted access lists has
475
access to the cluster. If the \fBuser_lists\fP parameter is set to
476
NONE (the default) any user has access not explicitly excluded
477
via the \fBxuser_lists\fP parameter described below.
478
If a user is contained both in an access list enlisted in \fBxuser_lists\fP
479
and \fBuser_lists\fP the user is denied access to the cluster.
481
Changes to \fBuser_lists\fP will take immediate effect
483
This value is a global configuration parameter only. It cannot be
484
overwritten by the execution host local configuration.
487
.SS "\fBxuser_lists \fP"
488
The \fBxuser_lists\fP parameter contains a comma separated list of
489
user access lists as described in
491
Each user contained in at least one of the enlisted access lists is denied
492
access to the cluster. If the \fBxuser_lists\fP parameter is set to
493
NONE (the default) any user has access.
494
If a user is contained both in an access list enlisted in \fBxuser_lists\fP
495
and \fBuser_lists\fP (see above) the user is denied access to the cluster.
497
Changes to \fBxuser_lists\fP will take immediate effect
499
This value is a global configuration parameter only. It cannot be
500
overwritten by the execution host local configuration.
503
.SS "\fBadministrator_mail\fP"
504
\fBadministrator_mail\fP specifies a comma separated list of the
505
electronic mail address(es) of the cluster administrator(s) to whom
506
internally-generated problem reports are sent. The mail address format
507
depends on your electronic mail system and how it is configured;
508
consult your system's configuration guide for more information.
510
Changing \fBadministrator_mail\fP takes immediate effect.
511
The default for \fBadministrator_mail\fP is an empty mail list.
513
This value is a global configuration parameter only. It cannot be
514
overwritten by the execution host local configuration.
519
The \fBprojects\fP list contains all projects which are granted access
520
to xxQS_NAMExx. User belonging to none of these projects cannot use xxQS_NAMExx. If
521
users belong to projects in the \fBprojects\fP list and the
522
\fBxprojects\fP list (see below), they also cannot use the system.
524
Changing \fBprojects\fP takes immediate effect.
525
The default for \fBprojects\fP is none.
527
This value is a global configuration parameter only. It cannot be
528
overwritten by the execution host local configuration.
531
.SS "\fBxprojects\fP"
532
The \fBxprojects\fP list contains all projects that are denied access
533
to xxQS_NAMExx. User belonging to one of these projects cannot use xxQS_NAMExx. If
534
users belong to projects in the \fBprojects\fP list (see above) and the
535
\fBxprojects\fP list, they also cannot use the system.
537
Changing \fBxprojects\fP takes immediate effect.
538
The default for \fBxprojects\fP is none.
540
This value is a global configuration parameter only. It cannot be
541
overwritten by the execution host local configuration.
544
.SS "\fBload_report_time\fP"
545
System load is reported periodically by the execution daemons to
546
.M xxqs_name_sxx_qmaster 8 .
547
The parameter \fBload_report_time\fP defines the time interval between load
551
.M xxqs_name_sxx_execd 8
552
may use a different load report time. Changing \fBload_report_time\fP will
553
take immediate effect.
555
\fBNote:\fP Be careful
556
when modifying \fBload_report_time\fP. Reporting load too frequently
558
.M xxqs_name_sxx_qmaster 8
559
especially if the number of execution hosts is large. Moreover, since the
560
system load typically increases and decreases smoothly, frequent load
561
reports hardly offer any benefit.
563
The default for \fBload_report_time\fP is 40 seconds.
565
The global configuration entry for this value
566
may be overwritten by the execution host local configuration.
569
.SS "\fBreschedule_unknown\fP"
570
Determines whether jobs on hosts in unknown state
571
are rescheduled and thus sent to other hosts. Hosts
572
are registered as unknown if
573
.M xxqs_name_sxx_master 8
574
cannot establish contact to the
575
.M xxqs_name_sxx_execd 8
578
). Likely reasons are a breakdown of
579
the host or a breakdown of the network connection in between, but also
580
.M xxqs_name_sxx_execd 8
581
may not be executing on such hosts.
583
In any case, xxQS_NAMExx can reschedule jobs running on such hosts to
585
.B reschedule_unknown
586
controls the time which
587
xxQS_NAMExx will wait before jobs are rescheduled after a host became
588
unknown. The time format specification is hh:mm:ss. If the special
589
value 00:00:00 is set, then jobs will not be rescheduled from this host.
591
Rescheduling is only initiated for jobs which have activated the rerun flag
600
Parallel jobs are only rescheduled if the host on which their
601
master task executes is in unknown state. The behaviour of
602
.B reschedule_unknown
603
for parallel jobs and for jobs without the rerun flag be set can be
604
adjusted using the \fBqmaster_params\fP settings
605
.B ENABLE_RESCHEDULE_KILL
607
.B ENABLE_RESCHEDULE_SLAVE.
609
Checkpointing jobs will only be
612
option of the corresponding checkpointing environment contains an
613
appropriate flag. (see
615
Interactive jobs (see
622
.B reschedule_unknown
625
The global configuration entry for this value may be over written by
626
the execution host local configuration.
629
.SS "\fBmax_unheard\fP"
631
.M xxqs_name_sxx_qmaster 8
632
could not contact or was not contacted by the execution daemon of a host
633
for \fBmax_unheard\fP seconds, all queues residing on that particular host
634
are set to status unknown.
635
.M xxqs_name_sxx_qmaster 8 ,
637
should be contacted by the execution daemons in order to get the load
638
reports. Thus, \fBmax_unheard\fP should by greater than the
639
\fBload_report_time\fP (see above).
641
Changing \fBmax_unheard\fP takes immediate effect.
642
The default for \fBmax_unheard\fP is 2 minutes 30 seconds.
644
This value is a global configuration parameter only. It cannot be
645
overwritten by the execution host local configuration.
649
This parameter specifies the level of detail that xxQS_NAMExx components such
651
.M xxqs_name_sxx_qmaster 8
653
.M xxqs_name_sxx_execd 8
654
use to produce informative, warning or error messages which are logged
655
to the \fImessages\fP files in the master and execution daemon
656
spool directories (see the description of the
657
\fBexecd_spool_dir\fP parameter above). The following message
658
levels are available:
661
All error events being recognized are logged.
663
.IP "\fIlog_warning\fP"
664
All error events being recognized and all detected signs of
665
potentially erroneous behavior are logged.
668
All error events being recognized, all detected signs of
669
potentially erroneous behavior and a variety of informative
672
Changing \fBloglevel\fP will take immediate effect.
674
The default for \fBloglevel\fP is \fIlog_info\fP.
676
This value is a global configuration parameter only. It cannot be
677
overwritten by the execution host local configuration.
680
.SS "\fBmax_aj_instances\fP"
681
This parameter defines the maximum amount of array task to be scheduled to
682
run simultaneously per array job. An instance of an array task will be
683
created within the master daemon when it gets a start order from the
684
scheduler. The instance will be destroyed when the array task finishes.
685
Thus the parameter provides control mainly over the memory consumption of
686
array jobs in the master and scheduler daemon. It is most useful for very
687
large clusters and very large array jobs. The default for this parameter
688
is 2000. The value 0 will deactivate this limit and will allow the
689
scheduler to start as many array job tasks as suitable resources are
690
available in the cluster.
692
Changing \fBmax_aj_instances\fP will take immediate effect.
694
This value is a global configuration parameter only. It cannot be
695
overwritten by the execution host local configuration.
698
.SS "\fBmax_aj_tasks\fP"
699
This parameter defines the maximum number of array job tasks within an array
701
.M xxqs_name_sxx_qmaster 8
702
will reject all array job submissions which request
705
array job tasks. The default for this parameter is 75000. The value 0
706
will deactivate this limit.
708
Changing \fBmax_aj_tasks\fP will take immediate effect.
710
This value is a global configuration parameter only. It cannot be
711
overwritten by the execution host local configuration.
714
.SS "\fBmax_u_jobs\fP"
715
The number of active (not finished) jobs which each xxQS_NAMExx user can
716
have in the system simultaneously is controlled by this parameter. A value
717
greater than 0 defines the limit. The default value 0 means "unlimited". If
720
limit is exceeded by a job submission then the submission command exits
721
with exit status 25 and an appropriate error message.
723
Changing \fBmax_u_jobs\fP will take immediate effect.
725
This value is a global configuration parameter only. It cannot be
726
overwritten by the execution host local configuration.
730
The number of active (not finished) jobs simultaneously allowed in xxQS_NAMExx
731
is controlled by this parameter. A value greater than 0 defines the limit.
732
The default value 0 means "unlimited". If the
734
limit is exceeded by a job submission then the submission command exits
735
with exit status 25 and an appropriate error message.
737
Changing \fBmax_jobs\fP will take immediate effect.
739
This value is a global configuration parameter only. It cannot be
740
overwritten by the execution host local configuration.
743
.SS "\fBmax_advance_reservations\fP"
744
The number of active (not finished) Advance Reservations simultaneously
745
allowed in xxQS_NAMExx is controlled by this parameter. A value greater
746
than 0 defines the limit. The default value 0 means "unlimited". If the
747
.B max_advance_reservations
748
limit is exceeded by an Advance Reservation request then the submission
749
command exits with exit status 25 and an appropriate error message.
751
Changing \fBmax_advance_reservations\fP will take immediate effect.
753
This value is a global configuration parameter only. It cannot be
754
overwritten by the execution host local configuration.
757
.SS "\fBenforce_project\fP"
758
If set to \fItrue\fB, users are required to request a project whenever
759
submitting a job. See the \fB\-P\fP option to
763
Changing \fBenforce_project\fP will take immediate effect.
764
The default for \fBenforce_project\fP is \fIfalse\fP.
767
This value is a global configuration parameter only. It cannot be
768
overwritten by the execution host local configuration.
771
.SS "\fBenforce_user\fP"
772
If set to \fItrue\fB, a
774
must exist to allow for job submission. Jobs are rejected if no corresponding user
777
If set to \fIauto\fB, a
779
object for the submitting user will automatically be created during
780
job submission, if one does not already exist. The \fBauto_user_oticket\fP,
781
\fBauto_user_fshare\fP, \fBauto_user_default_project\fP, and
782
\fBauto_user_delete_time\fP configuration parameters will be used as
783
default attributes of the new
787
Changing \fBenforce_user\fP will take immediate effect.
788
The default for \fBenforce_user\fP is \fIfalse\fP.
791
This value is a global configuration parameter only. It cannot be
792
overwritten by the execution host local configuration.
795
.SS "\fBauto_user_oticket\fP"
796
The number of override tickets to assign to automatically created
798
objects. User objects are created automatically if the
800
attribute is set to \fIauto\fP.
805
will affect any newly created user objects, but will not change user
806
objects created in the past.
808
This value is a global configuration parameter only. It cannot be
809
overwritten by the execution host local configuration.
812
.SS "\fBauto_user_fshare\fP"
813
The number of functional shares to assign to automatically created
815
objects. User objects are created automatically if the
817
attribute is set to \fIauto\fP.
822
will affect any newly created user objects, but will not change user
823
objects created in the past.
825
This value is a global configuration parameter only. It cannot be
826
overwritten by the execution host local configuration.
829
.SS "\fBauto_user_default_project\fP"
830
The default project to assign to automatically created
832
objects. User objects are created automatically if the
834
attribute is set to \fIauto\fP.
838
.B auto_user_default_project
839
will affect any newly created user objects, but will not change user
840
objects created in the past.
842
This value is a global configuration parameter only. It cannot be
843
overwritten by the execution host local configuration.
846
.SS "\fBauto_user_delete_time\fP"
847
The number of seconds of inactivity after which automatically created
849
objects will be deleted. User objects are created automatically if the
851
attribute is set to \fIauto\fP. If the user has no active or pending
852
jobs for the specified amount of time, the
853
object will automatically be deleted. A value of 0 can be used to
854
indicate that the automatically created user object is permanent and
855
should not be automatically deleted.
858
.B auto_user_delete_time
859
will affect the deletion time for all users with active jobs.
861
This value is a global configuration parameter only. It cannot be
862
overwritten by the execution host local configuration.
865
.SS "\fBset_token_cmd\fP"
866
This parameter is only present if your xxQS_NAMExx system is licensed
869
\fBSet_token_cmd\fP points to a command which sets and extends AFS
870
tokens for xxQS_NAMExx jobs. In the standard xxQS_NAMExx AFS
871
distribution, it is supplied as a script which expects two command line
872
parameters. It reads the token from STDIN, extends the token's
873
expiration time and sets the token:
877
<set_token_cmd> <user> <token_extend_after_seconds>
881
As a shell script this command will call the programs:
890
which are provided by your distributor as source code. The script looks as
895
--------------------------------
898
forge -u $1 -t $2 | SetToken
899
--------------------------------
903
Since it is necessary for \fIforge\fP to read the secret AFS server
904
key, a site might wish to replace the \fBset_token_cmd\fP script by a
905
command, which connects to a custom daemon at the AFS server. The
906
token must be forged at the AFS server and returned to the local
907
machine, where \fISetToken\fP is executed.
909
Changing \fBset_token_cmd\fP will take immediate effect.
910
The default for \fBset_token_cmd\fP is none.
912
The global configuration entry for this value
913
may be overwritten by the execution host local configuration.
917
This parameter is only present if your xxQS_NAMExx system is licensed
920
The path to your \fIpagsh\fB is specified via this parameter.
922
.M xxqs_name_sxx_shepherd 8
923
process and the job run in a \fIpagsh\fP. Please ask your AFS administrator
926
Changing \fBpag_cmd\fP will take immediate effect.
927
The default for \fBpag_cmd\fP is none.
929
The global configuration entry for this value
930
may be overwritten by the execution host local configuration.
933
.SS "\fBtoken_extend_time\fP"
934
This parameter is only present if your xxQS_NAMExx system is licensed
937
The \fBtoken_extend_time\fP is the time period for which AFS tokens are periodically
938
extended. xxQS_NAMExx
939
will call the token extension 30 minutes before the tokens expire until
940
jobs have finished and the corresponding tokens are no longer required.
942
Changing \fBtoken_extend_time\fP will take immediate effect.
943
The default for \fBtoken_extend_time\fP is 24:0:0, i.e. 24 hours.
945
The global configuration entry for this value
946
may be overwritten by the execution host local configuration.
949
.SS "\fBgid_range\fP"
951
is a comma separated list of range expressions of the form n-m (n as
952
well as m are integer numbers greater than 99), where m is an
953
abbreviation for m-m. These numbers are used in
954
.M xxqs_name_sxx_execd 8
955
to identify processes belonging to the same job.
958
.M xxqs_name_sxx_execd 8
959
may use a separate set up group ids for this purpose.
960
All number in the group id range have to be unused
961
supplementary group ids on the system, where the
962
.M xxqs_name_sxx_execd 8
965
Changing \fBgid_range\fP will take immediate effect.
966
There is no default for \fBgid_range\fP. The administrator will have to
967
assign a value for \fBgid_range\fP during installation of xxQS_NAMExx.
969
The global configuration entry for this value
970
may be overwritten by the execution host local configuration.
973
.SS "\fBqmaster_params\fP"
974
A list of additional parameters can be passed to the
975
xxQS_NAMExx qmaster. The following values are recognized:
976
.IP "\fIENABLE_FORCED_QDEL\fP"
977
If this parameter is set, non-administrative users can force deletion of
978
their own jobs via the \fI\-f\fP option of
980
Without this parameter, forced deletion of jobs is only allowed by the
981
xxQS_NAMExx manager or operator.
983
\fBNote:\fP Forced deletion for jobs is executed differently depending
984
on whether users are xxQS_NAMExx administrators or not. In case of
985
administrative users, the jobs are removed from the internal database of
986
xxQS_NAMExx immediately. For regular users, the equivalent of a normal
988
is executed first, and deletion is forced only if the normal cancellation
991
.IP "\fIFORBID_RESCHEDULE\fP"
992
If this parameter is set, re-queuing of jobs cannot
993
be initiated by the job script which is under control
994
of the user. Without this parameter jobs returning the
995
value 99 are rescheduled. This can be used to cause the
996
job to be restarted at a different machine, for instance if there
997
are not enough resources on the current one.
999
.IP "\fIFORBID_APPERROR\fP"
1000
If this parameter is set, the application cannot set itself to error state.
1001
Without this parameter jobs returning the value 100 are set to error state
1002
(and therefore can be manually rescheduled by clearing the error state).
1003
This can be used to set the job to error state when a starting condition
1004
of the application is not fulfilled before the application itself has been
1005
started, or when a clean up procedure (e.g. in the epilog) decides that it is
1006
necessary to run the job again, by returning 100 in the prolog, pe_start,
1007
job script, pe_stop or epilog script.
1009
.IP "\fIDISABLE_AUTO_RESCHEDULING\fP"
1010
If set to "true" or "1", the \fIreschedule_unknown\fP parameter
1011
is not taken into account.
1013
.IP "\fIENABLE_RESCHEDULE_KILL\fP"
1014
If set to "true" or "1", the \fIreschedule_unknown\fP parameter
1015
affects also jobs which have the rerun flag not activated
1024
but they are just finished as they can't be rescheduled.
1026
.IP "\fIENABLE_RESCHEDULE_SLAVE\fP"
1027
If set to "true" or "1" xxQS_NAMExx triggers job rescheduling also when
1028
the host where the slave tasks of a parallel job executes is in unknon state,
1029
if the \fIreschedule_unknown\fP parameter is activated.
1031
.IP "\fIMAX_DYN_EC\fP"
1032
Sets the max number of dynamic event clients (as used by qsub -sync y
1033
and by xxQS_NAMExx DRMAA API library sessions). The default is set to 99.
1034
The number of dynamic event clients should not be bigger than half of
1035
the number of file descriptors the system has. The number of file
1036
descriptors are shared among the connections to all exec hosts, all
1037
event clients, and file handles that the qmaster needs.
1039
.IP "\fIMONITOR_TIME\fP"
1040
Specifies the time interval when the monitoring information should be printed. The
1041
monitoring is disabled by default and can be enabled by specifying an interval.
1042
The monitoring is per thread and is written to the messages file or displayed by
1043
the "qping -f" command line tool. Example: MONITOR_TIME=0:0:10 generates and
1044
prints the monitoring information approximately every 10 seconds. The specified
1045
time is a guideline only and not a fixed interval. The interval that is actually
1046
used is printed. In this example, the interval could be anything between 9
1047
seconds and 20 seconds.
1049
.IP "\fILOG_MONITOR_MESSAGE\fP"
1050
Monitoring information is logged into the messages files by default. This
1051
information can be accessed via by
1053
If monitoring is always enabled, the messages files can become quite large.
1054
This switch disables logging into the messages files, making
1056
the only source of monitoring data.
1058
.IP "\fIPROF_SIGNAL\fP"
1059
Profiling provides the user with the possibility to get system measurements.
1060
This can be useful for debugging or optimization of the system. The profiling
1061
output will be done within the messages file.
1063
Enables the profiling for qmaster signal thread.
1064
(e.g. PROF_SIGNAL=true)
1066
.IP "\fIPROF_WORKER\fP"
1067
Enables the profiling for qmaster worker threads.
1068
(e.g. PROF_WORKER=true)
1070
.IP "\fIPROF_LISTENER\fP"
1071
Enables the profiling for qmaster listener threads.
1072
(e.g. PROF_LISTENER=true)
1074
.IP "\fIPROF_DELIVER\fP"
1075
Enables the profiling for qmaster event deliver thread.
1076
(e.g. PROF_DELIVER=true)
1078
.IP "\fIPROF_TEVENT\fP"
1079
Enables the profiling for qmaster timed event thread.
1080
(e.g. PROF_TEVENT=true)
1082
Please note, that the cpu utime and stime values contained in the profiling output
1083
are not per thread cpu times.
1084
These cpu usage statistics are per process statistics.
1085
So the printed profiling values for cpu mean "cpu time consumed by sge_qmaster (all threads) while the reported profiling level was active".
1086
.IP "\fISTREE_SPOOL_INTERVAL\fP"
1087
Sets the time interval for spooling the sharetree usage. The
1088
default is set to 00:04:00. The setting accepts colon-separated
1089
string or seconds. There is no setting to turn the sharetree spooling
1091
(e.g. STREE_SPOOL_INTERVAL=00:02:00)
1093
.IP "\fIMAX_JOB_DELETION_TIME\fp
1094
Sets the value of how long the qmaster will spend deleting jobs. After this time,
1095
the qmaster will continue with other tasks and schedule the deletion of remaining
1096
jobs at a later time. The default value is 3 seconds, and will be used if no value
1097
is entered. The range of valid values is > 0 and <= 5.
1098
(e.g. MAX_JOB_DELETION_TIME=1)
1100
.IP "\fIgdi_timeout\fp
1101
Sets how long the communication will wait for gdi send/receive operations.
1102
The default value is set to 60 seconds. After this time, the communication library will
1103
retry, if "gdi_retries" is configured, receiving the gdi request. In case of not configured
1104
"gdi_retries" the communication will return with a "gdi receive failure"
1105
(e.g. gdi_timeout=120 will set the timeout time to 120 sec)
1106
Configuring no gdi_timeout value, the value defaults to 60 sec.
1108
.IP "\fIgdi_retries\fp
1109
Sets how often the gdi receive call will be repeated until the gdi receive
1110
error appears. The default is set to 0. In this case the call will be done 1 time with no retry.
1111
Setting the value to -1 the call will be done permanently. In combination with gdi_timeout parameter
1112
it is possible to configure a system with eg. slow NFS, to make sure that all jobs will be submitted.
1113
(e.g. gdi_retries=4)
1116
Turns on/off a communication library ping. This parameter will create additional debug output.
1117
This output shows information about the error messages which are returned by communication
1118
and it will give information about the application status of the qmaster. eg, if it's unclear what's the
1119
reason for gdi timeouts, this may show you some useful messages. The default value is false (off)
1122
Changing \fBqmaster_params\fP will take immediate effect, except gdi_timeout, gdi_retries, cl_ping, these
1123
will take effect only for new connections.
1124
The default for \fBqmaster_params\fP is none.
1126
This value is a global configuration parameter only. It cannot be
1127
overwritten by the execution host local configuration.
1130
.SS "\fBexecd_params\fP"
1131
This is used for passing additional parameters
1132
to the xxQS_NAMExx execution daemon. The following values are recognized:
1134
.IP "\fIACCT_RESERVED_USAGE\fP"
1135
If this parameter is set to true, the usage of reserved resources is used for the
1136
accounting entries \fBcpu\fP, \fBmem\fP and \fBio\fP instead of the
1139
.IP "\fIENABLE_WINDOMACC\fP"
1140
If this parameter is set to true, Windows Domain accounts (WinDomAcc)
1141
are used on Windows hosts. These accounts require the use of
1145
If this parameter is set to false or is not set, local Windows accounts are used.
1146
On non-Windows hosts, this parameter is ignored.
1148
.IP "\fIKEEP_ACTIVE\fP"
1149
This value should only be set for debugging purposes. If set to true, the
1150
execution daemon will not remove the spool directory maintained by
1151
.M xxqs_name_sxx_shepherd 8
1154
.IP "\fIPTF_MIN_PRIORITY\fP, \fIPTF_MAX_PRIORITY\fP"
1155
The maximum/minimum priority which xxQS_NAMExx will assign to a job.
1156
Typically this is a negative/positive value in the range of -20
1157
(maximum) to 19 (minimum) for systems which allow setting of priorities
1160
system call. Other systems may provide different ranges.
1162
The default priority range (varies from system to system) is installed
1163
either by removing the parameters or by setting a value of -999.
1165
See the "messages" file of the execution daemon for the predefined
1166
default value on your hosts. The values are logged during the startup of
1167
the execution daemon.
1169
.IP "\fIPROF_EXECD\fP"
1170
Enables the profiling for the execution daemon.
1171
(e.g. PROF_EXECD=true)
1173
.IP "\fINOTIFY_KILL\fP"
1174
The parameter allows you to change the notification signal for
1175
the signal SIGKILL (see \fI\-notify\fP option of
1177
The parameter either accepts signal names (use the \fI\-l\fP option of
1179
or the special value \fInone\fP. If set to \fInone\fP,
1180
no notification signal will be sent. If it is set to \fITERM\fP, for
1181
instance, or another
1182
signal name then this signal will be sent as notification signal.
1184
.IP "\fINOTIFY_SUSP\fP"
1185
With this parameter it is possible to modify the notification signal
1186
for the signal SIGSTOP (see \fI\-notify\fP parameter of
1188
The parameter either accepts signal names (use the \fI\-l\fP option of
1190
or the special value \fInone\fP. If set to \fInone\fP,
1191
no notification signal will be sent. If it is set to \fITSTP\fP, for
1192
instance, or another
1193
signal name then this signal will be sent as notification signal.
1195
.IP "\fISHARETREE_RESERVED_USAGE\fP"
1196
If this parameter is set to true, the usage of reserved resources is taken for the
1197
xxQS_NAMExx share tree consumption instead of measured usage.
1199
.IP "\fIUSE_QSUB_GID\fP"
1200
If this parameter is set to true, the primary group id active when a
1201
job was submitted will be set to become the primary group id for job
1202
execution. If the parameter is not set, the primary group id as defined for
1203
the job owner in the execution host
1207
The feature is only available for jobs submitted via
1213
Also, it only works for
1215
jobs (and thus also for
1219
if rsh and rshd components are used which are provided with xxQS_NAMExx
1220
(i.e., the \fBrsh_daemon\fP and \fBrsh_command\fP parameters may
1221
not be changed from the default).
1224
.IP "\fIINHERIT_ENV\fP"
1225
This parameter indicates whether the shepherd should allow the environment
1226
inherited by the execution daemon from the shell that started it to be inherited
1227
by the job it's starting. When true, any environment variable that is set in
1228
the shell which starts the execution daemon at the time the execution daemon is
1229
started will be set in the environment of any jobs run by that execution daemon,
1230
unless the environment variable is explicitly overridden, such as PATH or
1231
LOGNAME. If set to false, each job starts with only the environment variables
1232
that are explicitly passed on by the execution daemon, such as PATH and LOGNAME.
1233
The default value is true.
1235
.IP "\fISET_LIB_PATH\fP"
1236
This parameter tells the execution daemon whether to add the xxQS_NAMExx shared
1237
library directory to the library path of executed jobs. If set to true, and
1238
INHERIT_ENV is also set to true, the xxQS_NAMExx shared library directory will
1239
be prepended to the library path which is inherited from the shell which started
1240
the execution daemon. If INHERIT_ENV is set to false, the library path will
1241
contain only the xxQS_NAMExx shared library directory. If set to false, and
1242
INHERIT_ENV is set to true, the library path exported to the job will be the one
1243
inherited from the shell which started the execution daemon. If INHERIT_ENV is
1244
also set to false, the library path will be empty. After the execution daemon
1245
has set the library path, it may be further altered by the shell in which the
1246
job is executed, or by the job script itself. The default value for
1247
SET_LIB_PATH is false.
1249
.IP "\fIENABLE_ADDGRP_KILL\fP"
1250
If this parameter is set then xxQS_NAMExx uses the supplementary group ids
1251
(see \fIgid_range\fP) to identify all processes which are to be terminated
1252
when a job is deleted, or when
1253
.M xxqs_name_sxx_shepherd 8
1254
cleans up after job termination.
1256
.IP "\fIPDC_INTERVAL\fP"
1257
This parameter defines the interval how often the PDC (Portable Data Collector)
1258
is executed by the execution daemon. The PDC is responsible for enforcing
1259
the resource limits s_cpu, h_cpu, s_vmem and h_vmem (see
1261
and job usage collection.
1262
The parameter can be set
1263
to a time_specifier (see
1265
, to \fBPER_LOAD_REPORT\fP or to \fBNEVER\fP.
1267
If this parameter is set to \fBPER_LOAD_REPORT\fP the PDC is triggered in the
1268
same interval as \fBload_report_time\fP (see above). If this parameter is set
1269
to \fBNEVER\fP the PDC run is never trigged. The default is 1 second.
1271
\fBNote:\fP A PDC run is quite compute extensive may degrade the
1272
performance of the running jobs. But if the PDC runs less often or never the
1273
online usage can be incomplete or totally missing (for example online usage of very short
1274
running jobs might be missing) and the resource limit enforcement is
1275
less accurate or would not happen if PDC is turned of completely.
1277
Changing \fBexecd_params\fP will take effect after it was propagated to the
1278
execution daemons. The propagation is done in one load report interval.
1279
The default for \fBexecd_params\fP is none.
1281
The global configuration entry for this value
1282
may be overwritten by the execution host local configuration.
1285
.SS "\fBreporting_params\fP"
1286
Used to define the behavior of reporting modules in the xxQS_NAMExx
1287
qmaster. Changes to the \fBreporting_params\fP takes immediate effect.
1288
The following values are recognized:
1290
.IP "\fIaccounting\fP"
1291
If this parameter is set to true, the accounting file is written.
1292
The accounting file is prerequisite for using the \fBqacct\fP command.
1294
.IP "\fIreporting\fP"
1295
If this parameter is set to true, the reporting file is written.
1296
The reporting file contains data that can be used for monitoring and analysis,
1297
like job accounting, job log, host load and consumables, queue status and
1298
consumables and sharetree configuration and usage.
1299
Attention: Depending on the size and load of the cluster, the reporting file can
1300
become quite large. Only activate the reporting file if you have a process running that will consume the reporting file!
1303
for further information about format and contents of the reporting file.
1305
.IP "\fIflush_time\fP"
1306
Contents of the reporting file are buffered in the
1307
xxQS_NAMExx qmaster and flushed at a fixed interval.
1308
This interval can be configured with the \fIflush_time\fP parameter.
1309
It is specified as a time value in the format HH:MM:SS.
1310
Sensible values range from a few seconds to one minute. Setting it too low may
1311
slow down the qmaster. Setting it too high will make the qmaster consume large
1312
amounts of memory for buffering data.
1314
.IP "\fIaccounting_flush_time\fP"
1315
Contents of the accounting file are buffered in the
1316
xxQS_NAMExx qmaster and flushed at a fixed interval.
1317
This interval can be configured with the \fIaccounting_flush_time\fP parameter.
1318
It is specified as a time value in the format HH:MM:SS.
1319
Sensible values range from a few seconds to one minute. Setting it too low may
1320
slow down the qmaster. Setting it too high will make the qmaster consume large
1321
amounts of memory for buffering data. Setting it to 00:00:00 will disable
1322
accounting data buffering; as soon as data is generated, it will be written to
1323
the accounting file. If this parameter is not set, the accounting data flush
1324
interval will default to the value of the \fIflush_time\fP parameter.
1327
If this parameter is set to true, the reporting file will contain job logging
1330
for more information about job logging.
1332
.IP "\fIsharelog\fP"
1333
The xxQS_NAMExx qmaster can dump information about sharetree configuration and use to the reporting file.
1334
The parameter \fIsharelog\fP sets an interval in which sharetree information will be dumped.
1335
It is set in the format HH:MM:SS. A value of 00:00:00 configures qmaster not to
1336
dump sharetree information. Intervals of several minutes up to hours are sensible values for this parameter.
1339
for further information about sharelog.
1341
.IP "\fIlog_consumables\fP"
1342
This parameter controls writing of consumable resources to the reporting file.
1343
When set to (\fBlog_consumables=true\fB)
1344
information about all consumable resources (their current usage and their capacity)
1346
to the reporting file, whenever a consumable resource changes either in definition,
1348
or when the usage of a consumable resource changes.
1349
When \fBlog_consumables\fB is set to \fBfalse\fB (default), only those variables will be written to the
1350
reporting file, that are configured in the \fBreport_variables\fB in the exec host configuration, see
1352
for further information about \fBreport_variables\fB.
1356
.SS "\fBfinished_jobs\fP"
1357
xxQS_NAMExx stores a certain number of \fIjust finished\fP jobs to provide
1358
post mortem status information. The \fBfinished_jobs\fP parameter defines the
1359
number of finished jobs stored. If this maximum number is reached, the
1360
eldest finished job will be discarded for every new job added to the
1363
Changing \fBfinished_jobs\fP will take immediate effect.
1364
The default for \fBfinished_jobs\fP is 0.
1366
This value is a global configuration parameter only. It cannot be
1367
overwritten by the execution host local configuration.
1370
.SS "\fBqlogin_daemon\fP"
1371
This parameter specifies the mechanism that is to be started on the
1374
request. Usually this is the builtin mechanism. It's also possible to
1375
configure an external executable by specifying the full qualified
1376
pathname, e.g. of the system's telnet daemon.
1378
Changing \fBqlogin_daemon\fP will take immediate effect.
1379
The default value for \fBqlogin_daemon\fP is builtin.
1381
The global configuration entry for this value
1382
may be overwritten by the execution host local configuration.
1384
Examples for the two allowed kinds of attributes are:
1386
qlogin_daemon builtin
1390
qlogin_daemon /usr/sbin/in.telnetd
1393
.SS "\fBqlogin_command\fP"
1394
This is the command to be executed on the client side of a
1397
Usually this is the builtin qlogin mechanism.
1398
It's also possible to configure an external mechanism, usually the absolute
1399
pathname of the system's telnet client program. It is automatically started
1400
with the target host and port number as parameters.
1402
Changing \fBqlogin_command\fP will take immediate effect.
1403
The default value for \fBqlogin_command\fP is builtin.
1405
The global configuration entry for this value
1406
may be overwritten by the execution host local configuration.
1408
Examples for the two allowed kinds of attributes are:
1410
qlogin_command builtin
1414
qlogin_command /usr/bin/telnetd
1417
.SS "\fBrlogin_daemon\fP"
1418
This parameter specifies the mechanism that is to be started on the server
1423
a command argument to be executed remotely.
1424
Usually this is the builtin mechanism. It's also possible to
1425
configure an externel executable by specifying the absolute pathname,
1426
e.g. of the system's rlogin daemon.
1430
will take immediate effect. The default for
1434
The global configuration entry for this value may be overwritten by the
1435
execution host local configuration.
1437
The allowed values are similar to the ones of the examples of
1441
.SS "\fBrlogin_command\fP"
1442
This is the mechansim to be executed on the client side of a
1446
a command argument to be executed remotely.
1447
Usually this is the builtin mechanism. If no value is given,
1448
a specialized xxQS_NAMExx component is used.
1449
The command is automatically started with the target host and port number
1451
The xxQS_NAMExx rlogin client has been extended
1452
to accept and use the port number argument. You can only use clients, such
1453
as \fIssh\fP, which also understand this syntax.
1457
will take immediate effect. The default value for
1461
The global configuration entry for this value may be overwritten by the
1462
execution host local configuration.
1464
In addition to the examples of
1466
, this value is allowed:
1471
.SS "\fBrsh_daemon\fP"
1472
This parameter specifies the mechanism that is to be started on the server
1477
a command argument to be executed remotely.
1478
Usually this is the builtin mechanism. If no value is given,
1479
a specialized xxQS_NAMExx component is used.
1483
will take immediate effect. The default value for
1487
The global configuration entry for this value may be overwritten by the
1488
execution host local configuration.
1490
In addition to the examples of
1492
, this value is allowed:
1497
.SS "\fBrsh_command\fP"
1498
This is the mechanism to be executed on the client side of a
1502
a command argument to be executed remotely.
1503
Usually this is the builtin mechanism. If no value is given,
1504
a specialized xxQS_NAMExx component is used. The command is
1505
automatically started with the target host and port number as parameters
1508
plus the command with its arguments to be
1509
executed remotely. The xxQS_NAMExx rsh client has been extended to accept
1510
and use the port number argument. You can only use clients, such as
1511
\fIssh\fP, which also understand this syntax.
1515
will take immediate effect. The default value for
1519
The global configuration entry for this value may be overwritten by the
1520
execution host local configuration.
1522
In addition to the examples of
1524
, this value is allowed:
1529
.SS "\fBdelegated_file_staging\fP"
1530
This flag must be set to "true" when the prolog and epilog are ready for
1531
delegated file staging, so that the DRMAA attribute 'drmaa_transfer_files'
1532
is supported. To establish delegated file staging, use the variables
1533
beginning with "$fs_..." in prolog and epilog to move the input, output
1534
and error files from one host to the other.
1535
When this flag is set to "false", no file staging is available
1536
for the DRMAA interface. File staging is currently implemented only via
1537
the DRMAA interface.
1538
When an error occurs while moving the input, output and error files, return
1539
error code 100 so that the error handling mechanism can handle the error
1540
correctly. (See also FORBID_APPERROR).
1543
.SS "\fBreprioritize\fP"
1544
This flag enables or disables the reprioritization of jobs based on their
1545
ticket amount. The \fBreprioritize_interval\fP in
1547
takes effect only if \fBreprioritize\fP is set to true. To turn off
1548
job reprioritization, the \fBreprioritize\fP flag must be set to false
1549
and the \fBreprioritize_interval\fP to 0 which is the default.
1551
This value is a global configuration parameter only. It cannot be
1552
overridden by the execution host local configuration.
1555
.SS "\fBlibjvm_path\fP"
1556
\fBlibjvm_path\fP is usually set during qmaster installation and points to the absolute path of libjvm.so.
1557
(or the corresponding library depending on your architecture - e.g. /usr/java/jre/lib/i386/server/libjvm.so) The referenced libjvm version must be at least 1.5.
1558
It is needed by the jvm qmaster thread only. If the java vm needs additional starting parameters they can be set in \fBadditional_jvm_args\fP. If the jvm thread is started at all can be defined in the
1560
file. If libjvm_path is empty or an incorrect path the jvm thread fails to start.
1562
The global configuration entry for this value may be overwritten by the
1563
execution host local configuration.
1566
.SS "\fBadditional_jvm_args\fP"
1567
\fBadditional_jvm_args\fP is usually set during qmaster installation.
1568
Details about possible values \fBadditional_jvm_args\fP can be found in the help output of the accompanying java command. This setting is normally not needed.
1570
The global configuration entry for this value may be overwritten by the
1571
execution host local configuration.
1575
.M xxqs_name_sxx_intro 1 ,
1582
.M drmaa_attributes 3 ,
1585
.M xxqs_name_sxx_execd 8 ,
1586
.M xxqs_name_sxx_qmaster 8 ,
1587
.M xxqs_name_sxx_shepherd 8 ,
1589
.I xxQS_NAMExx Installation and Administration Guide.
1593
.M xxqs_name_sxx_intro 1
1594
for a full statement of rights and permissions.
added
removed
doc/man/man5/sge_conf.5
