1.\"/* Copyright 1988,1990,1993,1994 by Paul Vixie 2.\" * All rights reserved 3.\" * 4.\" * Distribute freely, except: don't remove my name from the source or 5.\" * documentation (don't take credit for my work), mark your changes (don't 6.\" * get me blamed for your possible bugs), don't alter or remove this 7.\" * notice. May be sold if buildable source is provided to buyer. No 8.\" * warrantee of any kind, express or implied, is included with this 9.\" * software; use at your own risk, responsibility for damages (if any) to 10.\" * anyone resulting from the use of this software rests entirely with the 11.\" * user. 12.\" * 13.\" * Send bug reports, bug fixes, enhancements, requests, flames, etc., and 14.\" * I'll try to keep a version up to date. I can be reached as follows: 15.\" * Paul Vixie <paul@vix.com> uunet!decwrl!vixie!paul 16.\" */ 17.\"
| 1.\"/* Copyright 1988,1990,1993,1994 by Paul Vixie 2.\" * All rights reserved 3.\" * 4.\" * Distribute freely, except: don't remove my name from the source or 5.\" * documentation (don't take credit for my work), mark your changes (don't 6.\" * get me blamed for your possible bugs), don't alter or remove this 7.\" * notice. May be sold if buildable source is provided to buyer. No 8.\" * warrantee of any kind, express or implied, is included with this 9.\" * software; use at your own risk, responsibility for damages (if any) to 10.\" * anyone resulting from the use of this software rests entirely with the 11.\" * user. 12.\" * 13.\" * Send bug reports, bug fixes, enhancements, requests, flames, etc., and 14.\" * I'll try to keep a version up to date. I can be reached as follows: 15.\" * Paul Vixie <paul@vix.com> uunet!decwrl!vixie!paul 16.\" */ 17.\"
|
18.\" $Id$
| 18.\" $Id: crontab.5,v 1.4 1997/02/22 16:04:52 peter Exp $
|
19.\"
| 19.\"
|
20.TH CRONTAB 5 "24 January 1994" 21.UC 4 22.SH NAME 23crontab \- tables for driving cron 24.SH DESCRIPTION
| 20.Dd January 24, 1994 21.Dt CRONTAB 5 22.Os 23.Sh NAME 24.Nm crontab 25.Nd tables for driving cron 26.Sh DESCRIPTION
|
25A
| 27A
|
26.I crontab
| 28.Nm
|
27file contains instructions to the
| 29file contains instructions to the
|
28.IR cron (8)
| 30.Xr cron 8
|
29daemon of the general form: ``run this command at this time on this date''. 30Each user has their own crontab, and commands in any given crontab will be 31executed as the user who owns the crontab. Uucp and News will usually have 32their own crontabs, eliminating the need for explicitly running
| 31daemon of the general form: ``run this command at this time on this date''. 32Each user has their own crontab, and commands in any given crontab will be 33executed as the user who owns the crontab. Uucp and News will usually have 34their own crontabs, eliminating the need for explicitly running
|
33.IR su (1)
| 35.Xr su 1
|
34as part of a cron command.
| 36as part of a cron command.
|
35.PP
| 37.Pp
|
36Blank lines and leading spaces and tabs are ignored. Lines whose first 37non-space character is a pound-sign (#) are comments, and are ignored. 38Note that comments are not allowed on the same line as cron commands, since 39they will be taken to be part of the command. Similarly, comments are not 40allowed on the same line as environment variable settings.
| 38Blank lines and leading spaces and tabs are ignored. Lines whose first 39non-space character is a pound-sign (#) are comments, and are ignored. 40Note that comments are not allowed on the same line as cron commands, since 41they will be taken to be part of the command. Similarly, comments are not 42allowed on the same line as environment variable settings.
|
41.PP
| 43.Pp
|
42An active line in a crontab will be either an environment setting or a cron 43command. An environment setting is of the form,
| 44An active line in a crontab will be either an environment setting or a cron 45command. An environment setting is of the form,
|
44.PP
| 46.Pp
|
45 name = value
| 47 name = value
|
46.PP
| 48.Pp
|
47where the spaces around the equal-sign (=) are optional, and any subsequent 48non-leading spaces in
| 49where the spaces around the equal-sign (=) are optional, and any subsequent 50non-leading spaces in
|
49.I value
| 51.Em value
|
50will be part of the value assigned to
| 52will be part of the value assigned to
|
51.IR name .
| 53.Em name .
|
52The
| 54The
|
53.I value
| 55.Em value
|
54string may be placed in quotes (single or double, but matching) to preserve 55leading or trailing blanks.
| 56string may be placed in quotes (single or double, but matching) to preserve 57leading or trailing blanks.
|
56.PP
| 58.Pp
|
57Several environment variables are set up 58automatically by the
| 59Several environment variables are set up 60automatically by the
|
59.IR cron (8)
| 61.Xr cron 8
|
60daemon.
| 62daemon.
|
61SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd
| 63.Ev SHELL 64is set to 65.Pa /bin/sh , 66and 67.Ev LOGNAME 68and 69.Ev HOME 70are set from the 71.Pa /etc/passwd
|
62line of the crontab's owner.
| 72line of the crontab's owner.
|
63HOME and SHELL may be overridden by settings in the crontab; LOGNAME may not. 64.PP 65(Another note: the LOGNAME variable is sometimes called USER on BSD systems... 66on these systems, USER will be set also.) 67.PP 68In addition to LOGNAME, HOME, and SHELL, 69.IR cron (8) 70will look at MAILTO if it has any reason to send mail as a result of running 71commands in ``this'' crontab. If MAILTO is defined (and non-empty), mail is 72sent to the user so named. If MAILTO is defined but empty (MAILTO=""), no
| 73.Ev HOME 74and 75.Ev SHELL 76may be overridden by settings in the crontab; 77.Ev LOGNAME 78may not. 79.Pp 80(Another note: the 81.Ev LOGNAME 82variable is sometimes called 83.Ev USER 84on BSD systems... 85on these systems, 86.Ev USER 87will be set also). 88.Pp 89In addition to 90.Ev LOGNAME , 91.Ev HOME , 92and 93.Ev SHELL , 94.Xr cron 8 95will look at 96.Ev MAILTO 97if it has any reason to send mail as a result of running 98commands in ``this'' crontab. If 99.Ev MAILTO 100is defined (and non-empty), mail is 101sent to the user so named. If 102.Ev MAILTO 103is defined but empty (MAILTO=""), no
|
73mail will be sent. Otherwise mail is sent to the owner of the crontab. This
| 104mail will be sent. Otherwise mail is sent to the owner of the crontab. This
|
74option is useful if you decide on /bin/mail instead of /usr/lib/sendmail as 75your mailer when you install cron -- /bin/mail doesn't do aliasing, and UUCP
| 105option is useful if you decide on 106.Pa /bin/mail 107instead of 108.Pa /usr/lib/sendmail 109as 110your mailer when you install cron -- 111.Pa /bin/mail 112doesn't do aliasing, and UUCP
|
76usually doesn't read its mail.
| 113usually doesn't read its mail.
|
77.PP
| 114.Pp
|
78The format of a cron command is very much the V7 standard, with a number of 79upward-compatible extensions. Each line has five time and date fields, 80followed by a user name if this is the system crontab file, 81followed by a command. Commands are executed by
| 115The format of a cron command is very much the V7 standard, with a number of 116upward-compatible extensions. Each line has five time and date fields, 117followed by a user name if this is the system crontab file, 118followed by a command. Commands are executed by
|
82.IR cron (8)
| 119.Xr cron 8
|
83when the minute, hour, and month of year fields match the current time,
| 120when the minute, hour, and month of year fields match the current time,
|
84.I and
| 121.Em and
|
85when at least one of the two day fields (day of month, or day of week) 86match the current time (see ``Note'' below).
| 122when at least one of the two day fields (day of month, or day of week) 123match the current time (see ``Note'' below).
|
87.IR cron (8)
| 124.Xr cron 8
|
88examines cron entries once every minute. 89The time and date fields are:
| 125examines cron entries once every minute. 126The time and date fields are:
|
90.IP 91.ta 1.5i 92field allowed values 93.br 94----- -------------- 95.br 96minute 0-59 97.br 98hour 0-23 99.br 100day of month 1-31 101.br 102month 1-12 (or names, see below) 103.br 104day of week 0-7 (0 or 7 is Sun, or use names) 105.br 106.PP
| 127.Bd -literal -offset indent 128field allowed values 129----- -------------- 130minute 0-59 131hour 0-23 132day of month 1-31 133month 1-12 (or names, see below) 134day of week 0-7 (0 or 7 is Sun, or use names) 135.Ed 136.Pp
|
107A field may be an asterisk (*), which always stands for ``first\-last''.
| 137A field may be an asterisk (*), which always stands for ``first\-last''.
|
108.PP
| 138.Pp
|
109Ranges of numbers are allowed. Ranges are two numbers separated 110with a hyphen. The specified range is inclusive. For example, 1118-11 for an ``hours'' entry specifies execution at hours 8, 9, 10 112and 11.
| 139Ranges of numbers are allowed. Ranges are two numbers separated 140with a hyphen. The specified range is inclusive. For example, 1418-11 for an ``hours'' entry specifies execution at hours 8, 9, 10 142and 11.
|
113.PP
| 143.Pp
|
114Lists are allowed. A list is a set of numbers (or ranges) 115separated by commas. Examples: ``1,2,5,9'', ``0-4,8-12''.
| 144Lists are allowed. A list is a set of numbers (or ranges) 145separated by commas. Examples: ``1,2,5,9'', ``0-4,8-12''.
|
116.PP
| 146.Pp
|
117Step values can be used in conjunction with ranges. Following 118a range with ``/<number>'' specifies skips of the number's value 119through the range. For example, ``0-23/2'' can be used in the hours 120field to specify command execution every other hour (the alternative 121in the V7 standard is ``0,2,4,6,8,10,12,14,16,18,20,22''). Steps are 122also permitted after an asterisk, so if you want to say ``every two 123hours'', just use ``*/2''.
| 147Step values can be used in conjunction with ranges. Following 148a range with ``/<number>'' specifies skips of the number's value 149through the range. For example, ``0-23/2'' can be used in the hours 150field to specify command execution every other hour (the alternative 151in the V7 standard is ``0,2,4,6,8,10,12,14,16,18,20,22''). Steps are 152also permitted after an asterisk, so if you want to say ``every two 153hours'', just use ``*/2''.
|
124.PP
| 154.Pp
|
125Names can also be used for the ``month'' and ``day of week'' 126fields. Use the first three letters of the particular 127day or month (case doesn't matter). Ranges or 128lists of names are not allowed.
| 155Names can also be used for the ``month'' and ``day of week'' 156fields. Use the first three letters of the particular 157day or month (case doesn't matter). Ranges or 158lists of names are not allowed.
|
129.PP
| 159.Pp
|
130The ``sixth'' field (the rest of the line) specifies the command to be 131run. 132The entire command portion of the line, up to a newline or %
| 160The ``sixth'' field (the rest of the line) specifies the command to be 161run. 162The entire command portion of the line, up to a newline or %
|
133character, will be executed by /bin/sh or by the shell 134specified in the SHELL variable of the cronfile.
| 163character, will be executed by 164.Pa /bin/sh 165or by the shell 166specified in the 167.Ev SHELL 168variable of the cronfile.
|
135Percent-signs (%) in the command, unless escaped with backslash 136(\\), will be changed into newline characters, and all data 137after the first % will be sent to the command as standard 138input.
| 169Percent-signs (%) in the command, unless escaped with backslash 170(\\), will be changed into newline characters, and all data 171after the first % will be sent to the command as standard 172input.
|
139.PP
| 173.Pp
|
140Note: The day of a command's execution can be specified by two 141fields \(em day of month, and day of week. If both fields are 142restricted (ie, aren't *), the command will be run when
| 174Note: The day of a command's execution can be specified by two 175fields \(em day of month, and day of week. If both fields are 176restricted (ie, aren't *), the command will be run when
|
143.I either
| 177.Em either
|
144field matches the current time. For example, 145.br 146``30 4 1,15 * 5'' 147would cause a command to be run at 4:30 am on the 1st and 15th of each 148month, plus every Friday.
| 178field matches the current time. For example, 179.br 180``30 4 1,15 * 5'' 181would cause a command to be run at 4:30 am on the 1st and 15th of each 182month, plus every Friday.
|
149.SH EXAMPLE CRON FILE 150.nf
| 183.Sh EXAMPLE CRON FILE 184.Bd -literal
|
151 152# use /bin/sh to run commands, no matter what /etc/passwd says 153SHELL=/bin/sh 154# mail any output to `paul', no matter whose crontab this is 155MAILTO=paul 156# 157# run five minutes after midnight, every day 1585 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1 159# run at 2:15pm on the first of every month -- output mailed to paul 16015 14 1 * * $HOME/bin/monthly 161# run at 10 pm on weekdays, annoy Joe 1620 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?% 16323 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday" 1645 4 * * sun echo "run at 5 after 4 every sunday"
| 185 186# use /bin/sh to run commands, no matter what /etc/passwd says 187SHELL=/bin/sh 188# mail any output to `paul', no matter whose crontab this is 189MAILTO=paul 190# 191# run five minutes after midnight, every day 1925 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1 193# run at 2:15pm on the first of every month -- output mailed to paul 19415 14 1 * * $HOME/bin/monthly 195# run at 10 pm on weekdays, annoy Joe 1960 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?% 19723 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday" 1985 4 * * sun echo "run at 5 after 4 every sunday"
|
165.fi 166.SH SEE ALSO 167cron(8), crontab(1) 168.SH EXTENSIONS
| 199.Ed 200.Sh SEE ALSO 201.Xr cron 8 , 202.Xr crontab 1 203.Sh EXTENSIONS
|
169When specifying day of week, both day 0 and day 7 will be considered Sunday. 170BSD and ATT seem to disagree about this.
| 204When specifying day of week, both day 0 and day 7 will be considered Sunday. 205BSD and ATT seem to disagree about this.
|
171.PP
| 206.Pp
|
172Lists and ranges are allowed to co-exist in the same field. "1-3,7-9" would 173be rejected by ATT or BSD cron -- they want to see "1-3" or "7,8,9" ONLY.
| 207Lists and ranges are allowed to co-exist in the same field. "1-3,7-9" would 208be rejected by ATT or BSD cron -- they want to see "1-3" or "7,8,9" ONLY.
|
174.PP
| 209.Pp
|
175Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
| 210Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
|
176.PP
| 211.Pp
|
177Names of months or days of the week can be specified by name.
| 212Names of months or days of the week can be specified by name.
|
178.PP
| 213.Pp
|
179Environment variables can be set in the crontab. In BSD or ATT, the
| 214Environment variables can be set in the crontab. In BSD or ATT, the
|
180environment handed to child processes is basically the one from /etc/rc. 181.PP
| 215environment handed to child processes is basically the one from 216.Pa /etc/rc . 217.Pp
|
182Command output is mailed to the crontab owner (BSD can't do this), can be 183mailed to a person other than the crontab owner (SysV can't do this), or the 184feature can be turned off and no mail will be sent at all (SysV can't do this 185either).
| 218Command output is mailed to the crontab owner (BSD can't do this), can be 219mailed to a person other than the crontab owner (SysV can't do this), or the 220feature can be turned off and no mail will be sent at all (SysV can't do this 221either).
|
186.SH AUTHOR 187.nf 188Paul Vixie <paul@vix.com>
| 222.Sh AUTHOR 223.An Paul Vixie Aq paul@vix.com
|
| |