| [9] | 1 | .TH CRONTAB 1
|
|---|
| 2 | .SH NAME
|
|---|
| 3 | crontab \- User crontab manipulation
|
|---|
| 4 | .SH SYNOPSIS
|
|---|
| 5 | .B crontab \-c
|
|---|
| 6 | .RI [ user ]
|
|---|
| 7 | .I file
|
|---|
| 8 | .br
|
|---|
| 9 | .B crontab \-l
|
|---|
| 10 | .RI [ user ]
|
|---|
| 11 | .br
|
|---|
| 12 | .B crontab \-r
|
|---|
| 13 | .RI [ user ]
|
|---|
| 14 | .br
|
|---|
| 15 | .B crontab \-p
|
|---|
| 16 | .SH DESCRIPTION
|
|---|
| 17 | The
|
|---|
| 18 | .B crontab
|
|---|
| 19 | program allows users to manipulate their personal crontab files. These
|
|---|
| 20 | files are hidden in
|
|---|
| 21 | .BI /usr/spool/crontabs/ user
|
|---|
| 22 | where
|
|---|
| 23 | .I user
|
|---|
| 24 | is the login name of a given user. The system daemon
|
|---|
| 25 | .B cron
|
|---|
| 26 | uses these crontabs, among others, to run tasks that are to be repeated at
|
|---|
| 27 | regular intervals. See
|
|---|
| 28 | .BR crontab (5)
|
|---|
| 29 | on what a good crontab file should look like.
|
|---|
| 30 | .PP
|
|---|
| 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.
|
|---|
| 33 | .SH OPTIONS
|
|---|
| 34 | .TP
|
|---|
| 35 | \fB\-c\fR [\fIuser\fR] \fIfile\fR
|
|---|
| 36 | Install
|
|---|
| 37 | .I file
|
|---|
| 38 | as the crontab file of
|
|---|
| 39 | .IR user .
|
|---|
| 40 | .TP
|
|---|
| 41 | \fB\-l\fR [\fIuser\fR]
|
|---|
| 42 | List the crontab file of
|
|---|
| 43 | .I user
|
|---|
| 44 | to standard output.
|
|---|
| 45 | .TP
|
|---|
| 46 | \fB\-r\fR [\fIuser\fR]
|
|---|
| 47 | Remove the crontab file of
|
|---|
| 48 | .IR user .
|
|---|
| 49 | .TP
|
|---|
| 50 | \fB\-p\fR
|
|---|
| 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
|
|---|
| 53 | .B crontab
|
|---|
| 54 | program are signalled automatically. (Mnemonic: \-p = "ping".)
|
|---|
| 55 | .SH FILES
|
|---|
| 56 | .TP \w'/usr/spool/crontabs/user'u+5n
|
|---|
| 57 | .BI /usr/spool/crontabs/ user
|
|---|
| 58 | Per user personal crontab file.
|
|---|
| 59 | .SH "SEE ALSO"
|
|---|
| 60 | .BR crontab (5),
|
|---|
| 61 | .BR cron (8).
|
|---|
| 62 | .SH DIAGNOSTICS
|
|---|
| 63 | .B Crontab
|
|---|
| 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
|
|---|
| 66 | .B cron
|
|---|
| 67 | to reload are sent to standard output.
|
|---|
| 68 | .SH BUGS
|
|---|
| 69 | .B Crontab
|
|---|
| 70 | misses a
|
|---|
| 71 | .B \-e
|
|---|
| 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
|
|---|
| 75 | has a
|
|---|
| 76 | .B \-c
|
|---|
| 77 | option that installs a prepared crontab file. Use
|
|---|
| 78 | .PP
|
|---|
| 79 | .RS
|
|---|
| 80 | .nf
|
|---|
| 81 | crontab \-l >/tmp/tab
|
|---|
| 82 | ${EDITOR\-vi} /tmp/tab
|
|---|
| 83 | crontab \-c /tmp/tab
|
|---|
| 84 | .fi
|
|---|
| 85 | .RE
|
|---|
| 86 | .PP
|
|---|
| 87 | to get the same effect as
|
|---|
| 88 | .BR "crontab \-e" .
|
|---|
| 89 | .SH AUTHOR
|
|---|
| 90 | Kees J. Bot (kjb@cs.vu.nl)
|
|---|
| 91 |
|
|---|
| 92 | .\"
|
|---|
| 93 | .\" $PchId: crontab.1,v 1.3 2000/07/17 18:51:04 philip Exp $
|
|---|
