The following Hawkeye-related configuration variables control the cron capabilities of Condor. The cron mechanism is used to run executables (called modules) directly from the condor_startd daemon. The output of these modules is incorporated into the machine Class Ad generated by the condor_startd daemon.
STARTD_CRON_NAME
Defines a logical name and is used by the condor_startd daemon.
While not required, this macro makes Hawkeye-specific definitions
readable and maintainable. For example:
STARTD_CRON_NAME = Hawkeye
Defining this configuration variable in this way allows Condor
to refer to the job list by Hawkeye_JOBS,
rather than STARTD_CRON_JOBS. It also affects the
access to the individual job settings, such as setting the job's
environment, arguments, etc.
HAWKEYE_JOBS
The list of the jobs to be run either periodically or continuously,
when configuration variable STARTD_CRON_NAME is set to Hawkeye.
For uses other than Hawkeye, the attribute name would be STARTD_CRON_JOBS.
The configuration variable is defined by a list of jobs to run,
where items within the list are separated by tabs or newlines.
Each job in the list is of the form:
name:prefix:executable:period[:options]Each of these fields are described below:
Name is a logical name given to a module. This name
must be unique (no two modules may have the same name).
prefix
is used by Condor to form the names of
ClassAd attributes. It is a string that is prepended
to the attribute name that the module outputs.
For example, if the prefix is "xyz_", and an attribute name
output by a the module is "abc", then the resulting
attribute name generated by Condor for a ClassAd will be "xyz_abc".
executable is the full path name of the
executable to be run for this module. Note that multiple modules may
specify the same executable.
period specifies the timing of module
execution. For non-continuous modules (see below), this
specifies the period of time between successive executions of
the module. The value may be specified in seconds (append value with
the character 's'), in minutes (append value with the character 'm'),
or in hours (append value with the character 'h').
As an example, 5m starts the execution of the module every five
minutes. If no character is appended to the value, seconds are used
as a default. For continuous mode, the value has a different meaning.
It specifies the length of time after the module ceases execution
before it is restarted. A value of 0 is valid only in continuous mode.
continuous
is used to specify a module which runs in continous
mode (as described above). In continous mode, the condor_startd daemon
will attempt to keep the module running continuously; this is
used for modules that do not normally exit. If the
period is non-zero, the condor_startd daemon waits period seconds after
the module exits before restarting it.
nokill
For a non-continuous mode of module execution, the module may
still be running when the period is up and it is time to start
the module again.
The nokill option defines what to do in this case.
The nokill option allows the module to continue execution
if the period is up and the module is still running.
HAWKEYE_module_ARGS
The command line arguments to pass to the module,
when configuration variable STARTD_CRON_NAME
is set to Hawkeye.
HAWKEYE_module_ENV
The environment string to pass to the module,
when configuration variable STARTD_CRON_NAME
is set to Hawkeye.
The syntax is the same as that of DAEMONNAME_ENVIRONMENT.
HAWKEYE_module_CWD
The working directory in which to start the module,
when configuration variable STARTD_CRON_NAME
is set to Hawkeye.