1CRONTAB(5)                       File Formats                       CRONTAB(5)
2
3
4

NAME

6       crontab - files used to schedule the execution of programs
7

DESCRIPTION

9       A crontab file contains instructions for the cron(8) daemon in the fol‐
10       lowing simplified manner: "run this command at this time on this date".
11       Each  user can define their own crontab.  Commands defined in any given
12       crontab are executed under the user who owns that  particular  crontab.
13       Uucp and News usually have their own crontabs, eliminating the need for
14       explicitly running su(1) as part of a cron command.
15
16       Blank lines, leading spaces, and tabs are ignored.  Lines  whose  first
17       non-white space character is a pound-sign (#) are comments, and are not
18       processed.  Note that comments are not allowed on the same line as cron
19       commands,  since they are considered a part of the command.  Similarly,
20       comments are not allowed on the same line as environment variable  set‐
21       tings.
22
23       An  active line in a crontab is either an environment setting or a cron
24       command.  An environment setting is of the form:
25
26          name = value
27
28       where the white spaces around the equal-sign (=) are optional, and  any
29       subsequent  non-leading  white  spaces  in value is a part of the value
30       assigned to name.  The value string may be placed in quotes (single  or
31       double, but matching) to preserve leading or trailing white spaces.
32
33       Several  environment  variables are set up automatically by the cron(8)
34       daemon.  SHELL is set to /bin/sh, and LOGNAME and HOME are set from the
35       /etc/passwd  line  of the crontab´s owner.  HOME and SHELL can be over‐
36       ridden by settings in the crontab; LOGNAME can not.
37
38       (Note: the LOGNAME variable is sometimes called USER on BSD systems and
39       is also automatically set).
40
41       In  addition  to  LOGNAME, HOME, and SHELL, cron(8) looks at the MAILTO
42       variable if a mail needs to be send as a result of running any commands
43       in that particular crontab.  If MAILTO is defined (and non-empty), mail
44       is sent to the specified address.   If  MAILTO  is  defined  but  empty
45       (MAILTO=""),  no mail is sent.  Otherwise, mail is sent to the owner of
46       the crontab.  This option is useful if  you  decide  to  use  /bin/mail
47       instead  of /usr/lib/sendmail as your mailer.  Note that /bin/mail does
48       not provide aliasing and UUCP usually does not read its mail.  If MAIL‐
49       FROM  is  defined  (and  non-empty),  it is used as the envelope sender
50       address, otherwise, ``root'' is used.
51
52       By default, cron sends a  mail  using  the  'Content-Type:'  header  of
53       'text/plain' with the 'charset=' parameter set to the 'charmap/codeset'
54       of the locale in which crond(8) is started up, i.e., either the default
55       system  locale, if no LC_* environment variables are set, or the locale
56       specified by the LC_* environment variables (see locale(7)).  Different
57       character encodings can be used for mailing cron job outputs by setting
58       the CONTENT_TYPE and CONTENT_TRANSFER_ENCODING variables in  a  crontab
59       to the correct values of the mail headers of those names.
60
61       The  CRON_TZ variable specifies the time zone specific for the cron ta‐
62       ble.  The user should enter a time according to the specified time zone
63       into  the  table.   The  time used for writing into a log file is taken
64       from the local time zone, where the daemon is running.
65
66       The MLS_LEVEL environment variable provides support for  multiple  per-
67       job  SELinux  security  contexts in the same crontab.  By default, cron
68       jobs execute with the default SELinux security context of the user that
69       created  the  crontab  file.   When  using multiple security levels and
70       roles, this may not be sufficient, because the same user may be running
71       in  different roles or in different security levels.  For more informa‐
72       tion about roles and SELinux MLS/MCS, see selinux(8)  and  the  crontab
73       example  mentioned  later  on  in this text.  You can set the MLS_LEVEL
74       variable to the SELinux security context string specifying the particu‐
75       lar  SELinux  security context in which you want jobs to be run.  crond
76       will then set the execution context of those jobs that meet the  speci‐
77       fications  of  the  particular security context.  For more information,
78       see crontab(1) -s option.
79
80       The RANDOM_DELAY variable allows delaying job startups by random amount
81       of minutes with upper limit specified by the variable. The random scal‐
82       ing factor is determined during the cron daemon startup so  it  remains
83       constant for the whole run time of the daemon.
84
85       The format of a cron command is similar to the V7 standard, with a num‐
86       ber of upward-compatible extensions.  Each line has five  time-and-date
87       fields followed by a username (if this is the system crontab file), and
88       followed by a command.  Commands  are  executed  by  cron(8)  when  the
89       'minute',  'hour',  and  'month  of  the year' fields match the current
90       time, and at least one of the two 'day' fields ('day of month', or 'day
91       of week') match the current time (see "Note" below).
92
93       Note  that  this  means  that  non-existent times, such as the "missing
94       hours" during the daylight savings time conversion, will  never  match,
95       causing jobs scheduled during the "missing times" not to be run.  Simi‐
96       larly, times that occur more than once (again, during the daylight sav‐
97       ings time conversion) will cause matching jobs to be run twice.
98
99       cron(8) examines cron entries every minute.
100
101       The time and date fields are:
102
103              field          allowed values
104              -----          --------------
105              minute         0-59
106              hour           0-23
107              day of month   1-31
108              month          1-12 (or names, see below)
109              day of week    0-7 (0 or 7 is Sunday, or use names)
110
111       A   field  may  contain  an  asterisk  (*),  which  always  stands  for
112       "first-last".
113
114       Ranges of numbers are allowed.  Ranges are two numbers separated with a
115       hyphen.   The  specified  range is inclusive.  For example, 8-11 for an
116       'hours' entry specifies execution at hours 8, 9, 10, and 11. The  first
117       number must be less than or equal to the second one.
118
119       Lists are allowed.  A list is a set of numbers (or ranges) separated by
120       commas.  Examples: "1,2,5,9", "0-4,8-12".
121
122       Step values can be used in conjunction with ranges.  Following a  range
123       with  "/<number>"  specifies  skips  of  the number's value through the
124       range.  For example, "0-23/2" can be used in the 'hours' field to spec‐
125       ify  command  execution for every other hour (the alternative in the V7
126       standard is "0,2,4,6,8,10,12,14,16,18,20,22").  Step  values  are  also
127       permitted after an asterisk, so if specifying a job to be run every two
128       hours, you can use "*/2".
129
130       Names can also be used for the 'month' and 'day of week'  fields.   Use
131       the  first  three letters of the particular day or month (case does not
132       matter).  Ranges or lists of names are not allowed.
133
134       If the UID of the owner is 0 (root), the first character of  a  crontab
135       entry  can be "-" character. This will prevent cron from writing a sys‐
136       log message about the command being executed.
137
138       The "sixth" field (the rest of the line) specifies the  command  to  be
139       run.   The entire command portion of the line, up to a newline or a "%"
140       character, will be executed by /bin/sh or by the shell specified in the
141       SHELL variable of the cronfile.  A "%" character in the command, unless
142       escaped with a backslash (\), will be changed into newline  characters,
143       and  all data after the first % will be sent to the command as standard
144       input.
145
146       Note: The day of a command's execution can be specified in the  follow‐
147       ing two fields — 'day of month', and 'day of week'.  If both fields are
148       restricted (i.e., do not contain the "*" character), the  command  will
149       be run when either field matches the current time.  For example,
150       "30  4  1,15 * 5" would cause a command to be run at 4:30 am on the 1st
151       and 15th of each month, plus every Friday.
152

EXAMPLE CRON FILE

154       # use /bin/sh to run commands, no matter what /etc/passwd says
155       SHELL=/bin/sh
156       # mail any output to `paul', no matter whose crontab this is
157       MAILTO=paul
158       #
159       CRON_TZ=Japan
160       # run five minutes after midnight, every day
161       5 0 * * *       $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
162       # run at 2:15pm on the first of every month -- output mailed to paul
163       15 14 1 * *     $HOME/bin/monthly
164       # run at 10 pm on weekdays, annoy Joe
165       0 22 * * 1-5    mail -s "It's 10pm" joe%Joe,%%Where are your kids?%
166       23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday"
167       5 4 * * sun     echo "run at 5 after 4 every sunday"
168

Jobs in /etc/cron.d/

170       The jobs in cron.d and /etc/crontab are system  jobs,  which  are  used
171       usually  for  more  than  one  user, thus, additionally the username is
172       needed.  MAILTO on the first line is optional.
173

EXAMPLE OF A JOB IN /etc/cron.d/job

175       #login as root
176       #create job with preferred editor (e.g. vim)
177       MAILTO=root
178       * * * * * root touch /tmp/file
179

SELinux with multi level security (MLS)

181       In a crontab, it is important to specify a security level by crontab -s
182       or  specifying  the  required  level  on the first line of the crontab.
183       Each level is specified in /etc/selinux/targeted/seusers.   When  using
184       crontab in the MLS mode, it is especially important to:
185       - check/change the actual role,
186       - set correct role for directory, which is used for input/output.
187

EXAMPLE FOR SELINUX MLS

189       # login as root
190       newrole -r sysadm_r
191       mkdir /tmp/SystemHigh
192       chcon -l SystemHigh /tmp/SystemHigh
193       crontab -e
194       # write in crontab file
195       MLS_LEVEL=SystemHigh
196       0-59 * * * * id -Z > /tmp/SystemHigh/crontest
197

FILES

199       /etc/crontab  main  system  crontab file.  /var/spool/cron/ a directory
200       for storing crontabs defined by users.  /etc/cron.d/  a  directory  for
201       storing system crontabs.
202

SEE ALSO

204       cron(8), crontab(1)
205

EXTENSIONS

207       These  special  time specification "nicknames" which replace the 5 ini‐
208       tial time and date fields, and are prefixed with the '@' character, are
209       supported:
210
211       @reboot    :    Run once after reboot.
212       @yearly    :    Run once a year, ie.  "0 0 1 1 *".
213       @annually  :    Run once a year, ie.  "0 0 1 1 *".
214       @monthly   :    Run once a month, ie. "0 0 1 * *".
215       @weekly    :    Run once a week, ie.  "0 0 * * 0".
216       @daily     :    Run once a day, ie.   "0 0 * * *".
217       @hourly    :    Run once an hour, ie. "0 * * * *".
218

CAVEATS

220       crontab  files  have  to be regular files or symlinks to regular files,
221       they must not be executable or writable for anyone else but the  owner.
222       This  requirement can be overridden by using the -p option on the crond
223       command line.  If inotify support is in use, changes in  the  symlinked
224       crontabs  are  not  automatically noticed by the cron daemon.  The cron
225       daemon must receive a SIGHUP signal to reload the crontabs.  This is  a
226       limitation of the inotify API.
227
228       cron  requires that each entry in a crontab end in a newline character.
229       If the last entry in a crontab is missing a newline (i.e. terminated by
230       EOF),  cron  will  consider the crontab (at least partially) broken.  A
231       warning will be written to syslog.
232

AUTHOR

234       Paul Vixie ⟨vixie@isc.org⟩
235
236
237
238cronie                            2012-11-22                        CRONTAB(5)
Impressum