*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> cron (8)              
Title
Content
Arch
Section
 

CRON(8)

Contents


NAME    [Toc]    [Back]

     cron -- daemon to execute scheduled commands (Vixie Cron)

SYNOPSIS    [Toc]    [Back]

     cron [-s] [-o] [-x debugflag[,...]]

DESCRIPTION    [Toc]    [Back]

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

     The cron utility searches /var/cron/tabs for crontab files which are
     named after accounts in /etc/passwd; crontabs found are loaded into memory.
  The cron utility also searches for /etc/crontab which is in a different
 format (see crontab(5)).  The cron utility then wakes up every
     minute, examining all stored crontabs, checking each command to see if it
     should be run in the current minute.  When executing 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
     modification time (or the modification time on /etc/crontab) has changed,
     and if it has, cron will then examine the modification time 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 modification time of the spool directory whenever it
     changes a crontab.

     Available options:

     -s      Enable special handling of situations when the GMT offset of the
	     local timezone changes, such as the switches between the standard
	     time and daylight saving time.

	     The jobs run during the GMT offset changes time as intuitively
	     expected.	If a job falls into a time interval that disappears
	     (for example, during the switch from standard time) to daylight
	     saving time or is duplicated (for example, during the reverse
	     switch), then it's handled in one of two ways:

	     The first case is for the jobs that run every at hour of a time
	     interval overlapping with the disappearing or duplicated interval.
  In other words, if the job had run within one hour before
	     the GMT offset change (and cron was not restarted nor the
	     crontab(5) changed after that) or would run after the change at
	     the next hour.  They work as always, skip the skipped time or run
	     in the added time as usual.

	     The second case is for the jobs that run less frequently.	They
	     are executed exactly once, they are not skipped nor executed
	     twice (unless cron is restarted or the user's crontab(5) is
	     changed during such a time interval).  If an interval disappears
	     due to the GMT offset change, such jobs are executed at the same
	     absolute point of time as they would be in the old time zone.
	     For example, if exactly one hour disappears, this point would be
	     during the next hour at the first minute that is specified for
	     them in crontab(5).

     -o      Disable the special handling of situations when the GMT offset of
	     the local timezone changes, to be compatible with the old
	     (default) behavior.  If both options -o and -s are specified, the
	     option specified last wins.

     -x debugflag[,...]
	     Enable writing of debugging information to standard output.  One
	     or more of the following comma separated debugflag identifiers
	     must be specified:

	     bit   currently not used
	     ext   make the other debug flags more verbose
	     load  be verbose when loading crontab files
	     misc  be verbose about miscellaneous one-off events
	     pars  be verbose about parsing individual crontab lines
	     proc  be verbose about the state of the process, including all of
		   its offspring
	     sch   be verbose when iterating through the scheduling algorithms
	     test  trace through the execution, but do not perform any actions

SEE ALSO    [Toc]    [Back]

      
      
     crontab(1), crontab(5)

AUTHORS    [Toc]    [Back]

     Paul Vixie <paul@vix.com>


FreeBSD 5.2.1		       December 20, 1993		 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
crontab Tru64 Submits a schedule of commands to cron
queuedefs Tru64 Queue description file for at, batch, and cron commands
dh_installcron Linux install cron scripts into etc/cron.*
VkCmdManager IRIX execute commands
at IRIX execute commands at a later time
at HP-UX execute batched commands immediately or at a later time
batch HP-UX execute batched commands immediately or at a later time
hosts.equiv Tru64 A file containing the names of remote systems and users that can execute commands on the local syste...
rpc_intro HP-UX Introduction to DCE RPC daemon and RPC control program commands
Xqtdir Tru64 Contains temporary files used by the uuxqt daemon to execute remote command requests
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service