1cron(1M) System Administration Commands cron(1M)
2
3
4
6 cron - clock daemon
7
9 /usr/sbin/cron
10
11
13 cron starts a process that executes commands at specified dates and
14 times.
15
16
17 You can specify regularly scheduled commands to cron according to
18 instructions found in crontab files in the directory
19 /var/spool/cron/crontabs. Users can submit their own crontab file using
20 the crontab(1) command. Commands which are to be executed only once can
21 be submitted using the at(1) command.
22
23
24 cron only examines crontab or at command files during its own process
25 initialization phase and when the crontab or at command is run. This
26 reduces the overhead of checking for new or changed files at regularly
27 scheduled intervals.
28
29
30 As cron never exits, it should be executed only once. This is done rou‐
31 tinely by way of the svc:/system/cron:default service. The file
32 /etc/cron.d/FIFO file is used as a lock file to prevent the execution
33 of more than one instance of cron.
34
35
36 cron captures the output of the job's stdout and stderr streams, and,
37 if it is not empty, mails the output to the user. If the job does not
38 produce output, no mail is sent to the user. An exception is if the job
39 is an at(1) job and the -m option was specified when the job was sub‐
40 mitted.
41
42
43 cron and at jobs are not executed if your account is locked. Jobs and
44 processses execute. The shadow(4) file defines which accounts are not
45 locked and will have their jobs and processes executed.
46
47 Setting cron Jobs Across Timezones
48 The timezone of the cron daemon sets the system-wide timezone for cron
49 entries. This, in turn, is by set by default system-wide using
50 /etc/default/init. The timezone for cron entries can be overridden in a
51 user's crontab file; see crontab(1).
52
53
54 If some form of daylight savings or summer/winter time is in effect,
55 then jobs scheduled during the switchover period could be executed
56 once, twice, or not at all.
57
58 Setting cron Defaults
59 To keep a log of all actions taken by cron, you must specify CRON‐
60 LOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no
61 logging is done. Keeping the log is a user configurable option since
62 cron usually creates huge log files.
63
64
65 You can specify the PATH for user cron jobs by using PATH= in
66 /etc/default/cron. You can set the PATH for root cron jobs using
67 SUPATH= in /etc/default/cron. Carefully consider the security implica‐
68 tions of setting PATH and SUPATH.
69
70
71 Example /etc/default/cron file:
72
73 CRONLOG=YES
74 PATH=/usr/bin:/usr/ucb:
75
76
77
78
79 This example enables logging and sets the default PATH used by non-root
80 jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
81 /usr/sbin:/usr/bin.
82
83
84 The cron log file is periodically rotated by logadm(1M).
85
87 /etc/cron.d Main cron directory
88
89
90 /etc/cron.d/FIFO Lock file
91
92
93 /etc/default/cron cron default settings file
94
95
96 /var/cron/log cron history information
97
98
99 /var/spool/cron Spool area
100
101
102 /etc/cron.d/queuedefs Queue description file for at, batch, and cron
103
104
105 /etc/logadm.conf Configuration file for logadm
106
107
109 See attributes(5) for descriptions of the following attributes:
110
111
112
113
114 ┌─────────────────────────────┬─────────────────────────────┐
115 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
116 ├─────────────────────────────┼─────────────────────────────┤
117 │Availability │SUNWcsu │
118 └─────────────────────────────┴─────────────────────────────┘
119
121 svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M),
122 queuedefs(4), shadow(4), attributes(5), rbac(5), smf(5), smf_secu‐
123 rity(5)
124
126 The cron service is managed by the service management facility, smf(5),
127 under the service identifier:
128
129 svc:/system/cron:default
130
131
132
133
134 Administrative actions on this service, such as enabling, disabling, or
135 requesting restart, can be performed using svcadm(1M). The service's
136 status can be queried using the svcs(1) command. Most administrative
137 actions may be delegated to users with the solaris.smf.manage.cron
138 authorization (see rbac(5) and smf_security(5)).
139
141 A history of all actions taken by cron is stored in /var/cron/log and
142 possibly in /var/cron/olog.
143
144
145
146SunOS 5.11 4 Feb 2009 cron(1M)