
Comments begin with a pound sign (#) character and continue to the end of the line. All blank lines are ignored. Activity requests are indicated by keywords, all of which begin with the dollar sign ($) character.
In the descriptions of the activities, the definitions in the following table apply:
Term  | 
Description  | 
Comments  | 
{process}  | 
The ASCII name of a process appearing in the Bulletin Board  | 
|
{runlevels}  | 
Specifies which run levels to use to perform the activity  | 
The syntax is the same as used by init, that is, 4 = run level 4, 234 = run levels 2, 3, or 4  | 
{checkPeriod/Time}  | 
Indicates the activities performed repetitively have a specification of either: how often to perform the activity, or at what times of the day or week to perform the activity  | 
One of three forms is used: 
  | 
All five elements are required for the specification to be accepted. Each element can be one of items described in the following table:
Items  | 
Description  | 
*  | 
All items in class (days of the month, hours in the day, and so on)  | 
N  | 
The specific item  | 
N-M  | 
The items between N and M inclusive  | 
N,M  | 
The individual items N and M in the class  | 
The items within each class are defined in the following table:
Item  | 
Values  | 
{monthday}  | 
1-31  | 
{weekday}  | 
ASCII day of the week (sun, mon,...)  | 
{hour}  | 
0-23  | 
{min}  | 
0-59  | 
{sec}  | 
0-59  | 
For example: " * * * 0 0 " means perform each hour on the hour. "13 fri 12 0 0" means perform the activity at noon on any Friday the 13th.
The {cmd} command is executed if the activity so dictates. Within the command itself, there are four meta-words that can be used to generate flexible commands. Not all four meta-words have meaning in all cases. The meta-words are defined in the following table:
Meta-word  | 
Definition  | 
%f  | 
The full file name  | 
%d  | 
The directory portion of the file name  | 
%b  | 
The base name of the file name  | 
%p  | 
The process identification (PID) of the process  |