3 crontab \- User crontab manipulation
19 program allows users to manipulate their personal crontab files. These
21 .BI /usr/spool/crontabs/ user
24 is the login name of a given user. The system daemon
26 uses these crontabs, among others, to run tasks that are to be repeated at
27 regular intervals. See
29 on what a good crontab file should look like.
31 Only the superuser can specify a user name to manipulate the crontab of a
32 given user. Any other user can only touch their own crontab file.
35 \fB\-c\fR [\fIuser\fR] \fIfile\fR
38 as the crontab file of
41 \fB\-l\fR [\fIuser\fR]
42 List the crontab file of
46 \fB\-r\fR [\fIuser\fR]
47 Remove the crontab file of
51 Tell cron to reload its tables. Useful for system administrators to signal
52 a change to any of the system crontab files. Changes made by the
54 program are signalled automatically. (Mnemonic: \-p = "ping".)
56 .TP \w'/usr/spool/crontabs/user'u+5n
57 .BI /usr/spool/crontabs/ user
58 Per user personal crontab file.
64 preparses a new crontab and only installs it if correct. All errors are
65 sent to standard error, messages about installing a new table and telling
67 to reload are sent to standard output.
72 option that other implementations of this command allow one to edit the
73 current crontab and install the result. Seems quite handy until you try to
74 install a new crontab from an automated script. That's why this command
77 option that installs a prepared crontab file. Use
82 ${EDITOR\-vi} /tmp/tab
87 to get the same effect as
90 Kees J. Bot (kjb@cs.vu.nl)
93 .\" $PchId: crontab.1,v 1.3 2000/07/17 18:51:04 philip Exp $