cron(8) [minix man page]

CRON(8) 						      System Manager's Manual							   CRON(8)

NAME

       cron - clock daemon

SYNOPSIS

       cron

EXAMPLES

       /usr/bin/cron	   # Use absolute path in /etc/rc

DESCRIPTION

       Cron  is  clock	daemon.   It  is typically started up by including the command /usr/bin/cron in the /etc/rc file.  Once started, cron puts
       itself in the background, so no & is needed.  It runs forever, sleeping most of	the  time.   Once  a  minute  it  wakes  up  and  examines
       /usr/lib/crontab  to  see  if  there is any work to do.	If there is, the work is done.	The entries of /usr/lib/crontab contain 6 elements
       each.  Some examples follow:

	Min   Hr Dat	 Mo		       DayCommand
	 *  *  *  *  *	 /usr/bin/date >/dev/log   #print date every minute
	 0  *  *  *  *	 /usr/bin/date >/dev/log   #print date on the hour
	30  4  *  * 1-5  /bin/backup /dev/fd1	   #do backup Mon-Fri at 0430
	30 19  *  * 1,3,5		       /etc/backup /dev/fd1	 #Mon, Wed, Fri at 1930
	 0  9 25 12  *	 /usr/bin/sing >/dev/log   #Xmas morning at 0900 only

SEE ALSO

       at(1).

																	   CRON(8)

CRON(8) 						      System Manager's Manual							   CRON(8)

NAME

       cron - daemon to execute scheduled commands (Vixie Cron)

SYNOPSIS

       cron

DESCRIPTION

       Cron should be started from /etc/rc or /etc/rc.local.  It will return immediately, so you don't need to start it with '&'.

       Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory.  Cron
       also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see  crontab(5)).	Cron  then
       wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute.  When execut-
       ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,	if
       such exists).

       Additionally,  cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
       cron will then examine the modtime on all crontabs and reload those which have changed.	Thus cron need not be restarted whenever a crontab
       file is modified.  Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.

SEE ALSO

       crontab(1), crontab(5)

AUTHOR

       Paul Vixie <paul@vix.com>

4th Berkeley Distribution					 20 December 1993							   CRON(8)