Open System Services Shell and Utilities Reference Manual (G06.29+, H06.08+, J06.03+)

cron(8) OSS Shell and Utilities Reference Manual
where the variable information denotes the year, month, day, hour, minute, and second at which
the file was renamed.
The cron daemon starts each job with the following process attributes stored with the job by the
invoking process:
• Effective and real user IDs
• Effective and real group IDs
• Supplementary groups
Environment Variables
cron runs as a named process if the CRON_NAMED environment variable is set and exported
before the cron command is entered. The environment variable has the form:
CRON_NAMED=/G/process_name
where process_name conforms to the rules for Guardian process names described in the path-
name(5) reference page, available either online or in the Open System Services System Calls
Reference Manual. The following additional rules apply:
• The process name must be specified in OSS pathname format, so the $ is omitted
• The first character cannot be a Z
When CRON_NAMED is not defined or is not exported, cron starts as an unnamed process and
nothing prevents the undesirable situation of accidentally running multiple copies.
EXAMPLES
1. These SCF commands configure and start the cron process as a persistent process:
-> ASSUME $ZZKRN
-> ADD PROC #cro, &
NAME $cro, &
CPU FIRST, &
ASSOCPROC $cro1, &
PRIORITY 100, &
STARTUPMSG "-osstty -name /G/cro1 -p /bin/cron -f",&
PROGRAM $system.system.osh, &
HOMETERM $ZHOME, &
INFILE $NULL, &
OUTFILE $ZHOME, &
STARTMODE manual, &
AUTORESTART 3
-> START PROC #cro
2. This set of commands starts cron as the named process $CRON if another copy of cron
is not already running with the same name:
export CRON_NAMED=/G/CRON
cron
FILES
/bin/cron cron daemon code file.
/var/adm/cron/queuedefs
queue description file for at, batch, and cron.
12−6 Hewlett-Packard Company 527188-021