Configuration File for vovagent
For cases where the vovtaskers are started by submitting the
binary to a separate batch queue system such as LSF or SGE, the system administrator may
decide to use vovagent, which is a special copy of the vovtasker binary.
When vovagent is invoked, the binary limits the values of attributes
that are based on the information stored in the configuration file
$VOVDIR/local/vovagent.cfg to ensure compliance with the
underlying batch queue system's FairShare policies.
The contents of the configuration file and relation to the command line and
taskers.tcl file parameters are as
follows:
| Attribute Name | vovtasker options | vovagent.cfg option | Description |
|---|---|---|---|
| maxidle | -z | maxIdleTime | After being idle for the given time, tasker does not accept new jobs and exits after completing active jobs. Value is a VOV timespec, for example, 2m. The minimum value is 10s, and the maximum is the value of the maxlife parameter or 1hour, whichever is less. If the configuration file is absent or does not specify a value, the default is 1m. |
| maxlife | -Z | maxLifeTime | After the specified lifetime, tasker does not accept new jobs and exits after completing active jobs. The value is a VOV timespec, for example, 2H. The minimum value is 5m, and the maximum of unlimited is specified by giving 0 (zero) or a negative value. If the configuration file is absent or does not specify a value, the default is 2H. |
| update | -U | update | Specifies the update cycle time for the vovtasker agent, which is the interval at which tasker resource procedures are recalculated. The minimum value is 5s, and the maximum is half the value of the maxidle parameter or 5 minutes, whichever is less. If the configuration file is absent or does not specify a value, the default is 1m. |
An example of the vovagent configuration file is shown below.
Note: Set access permissions to ensure that only the VOV system manager account can
modify this file.
maxIdleTime = 1m
maxLifeTime = 1h
updateInterval = 15s