crontab.1 (59a3c79da68b53e9d606f0b7991574d982a843e1) crontab.1 (84f33dea627930e57209583fc83ffb3202babc0a)
1.\"/* Copyright 1988,1990,1993 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 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.\" $FreeBSD$
18.\" $Id: crontab.1,v 2.4 1993/12/31 10:47:33 vixie Exp $
19.\"
19.\"
20.Dd December 29, 1993
21.Dt CRONTAB 1
22.Os
23.Sh NAME
24.Nm crontab
25.Nd maintain crontab files for individual users (V3)
26.Sh SYNOPSIS
27.Nm
28.Op Fl u Ar user
29.Ar file
30.Nm
31.Op Fl u Ar user
32{
33.Fl l |
34.Fl r |
35.Fl e
36}
37.Sh DESCRIPTION
38The
39.Nm
40utility is the program used to install, deinstall or list the tables
20.TH CRONTAB 1 "29 December 1993"
21.UC 4
22.SH NAME
23crontab \- maintain crontab files for individual users (V3)
24.SH SYNOPSIS
25crontab [ -u user ] file
26.br
27crontab [ -u user ] { -l | -r | -e }
28.SH DESCRIPTION
29.I Crontab
30is the program used to install, deinstall or list the tables
41used to drive the
31used to drive the
42.Xr cron 8
43daemon in Vixie Cron.
44Each user can have their own crontab, and though
45these are files in
46.Pa /var ,
47they are not intended to be edited directly.
48.Pp
32.IR cron (8)
33daemon in Vixie Cron. Each user can have their own crontab, and though
34these are files in /var, they are not intended to be edited directly.
35.PP
49If the
36If the
50.Pa allow
37.I allow
51file exists, then you must be listed therein in order to be allowed to use
38file exists, then you must be listed therein in order to be allowed to use
52this command.
53If the
54.Pa allow
39this command. If the
40.I allow
55file does not exist but the
41file does not exist but the
56.Pa deny
57file does exist, then you must
58.Em not
59be listed in the
60.Pa deny
61file in order to use this command.
62If neither of these files exists, then
42.I deny
43file does exist, then you must \fBnot\fR be listed in the
44.I deny
45file in order to use this command. If neither of these files exists, then
63depending on site-dependent configuration parameters, only the super user
64will be allowed to use this command, or all users will be able to use this
65command.
46depending on site-dependent configuration parameters, only the super user
47will be allowed to use this command, or all users will be able to use this
48command.
66The format of these files is one username per line,
67with no leading or trailing whitespace.
68Lines of other formats will be ignored,
69and so can be used for comments.
70.Pp
71The first form of this command is used to install a new crontab from some
72named file or standard input if the pseudo-filename
73.Sq Fl
74is given.
75.Pp
76The following options are available:
77.Bl -tag -width indent
78.It Fl u
79Specify the name of the user whose crontab is to be
80tweaked.
81If this option is not given,
82.Nm
83examines
84.Dq your
85crontab, i.e., the crontab of the person executing the
86command.
87Note that
88.Xr su 1
49.PP
50If the
51.I -u
52option is given, it specifies the name of the user whose crontab is to be
53tweaked. If this option is not given,
54.I crontab
55examines "your" crontab, i.e., the crontab of the person executing the
56command. Note that
57.IR su (8)
89can confuse
58can confuse
90.Nm
59.I crontab
91and that if you are running inside of
60and that if you are running inside of
92.Xr su 1
61.IR su (8)
93you should always use the
62you should always use the
94.Fl u
63.I -u
95option for safety's sake.
64option for safety's sake.
96.It Fl l
97Display the current crontab on standard output.
98.It Fl r
99Remove the current crontab.
100.It Fl e
101Edit the current crontab using the editor specified by
102the
103.Ev VISUAL
104or
105.Ev EDITOR
106environment variables.
107The specified editor
108.Em must
109edit the file in place;
110any editor that unlinks the file and recreates it cannot be used.
111After you exit
65.PP
66The first form of this command is used to install a new crontab from some
67named file or standard input if the pseudo-filename ``-'' is given.
68.PP
69The
70.I -l
71option causes the current crontab to be displayed on standard output.
72.PP
73The
74.I -r
75option causes the current crontab to be removed.
76.PP
77The
78.I -e
79option is used to edit the current crontab using the editor specified by
80the \s-1VISUAL\s+1 or \s-1EDITOR\s+1 environment variables. After you exit
112from the editor, the modified crontab will be installed automatically.
81from the editor, the modified crontab will be installed automatically.
113.El
114.Sh FILES
115.Bl -tag -width /var/cron/allow -compact
116.It Pa /var/cron/allow
117.It Pa /var/cron/deny
118.El
119.Sh DIAGNOSTICS
120A fairly informative usage message appears if you run it with a bad command
121line.
122.Sh SEE ALSO
123.Xr crontab 5 ,
124.Xr cron 8
125.Sh STANDARDS
82.SH "SEE ALSO"
83crontab(5), cron(8)
84.SH FILES
85.nf
86/var/cron/allow
87/var/cron/deny
88.fi
89.SH STANDARDS
126The
90The
127.Nm
128command conforms to
129.St -p1003.2
130with the exception that the dangerous variant of calling
131.Nm
132without a file name in the first form of the command is not allowed by
133this implementation.
134The pseudo-filename
135.Sq Fl
136must be specified to read from standard input.
137The new command syntax
91.I crontab
92command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax
138differs from previous versions of Vixie Cron, as well as from the classic
139SVR3 syntax.
93differs from previous versions of Vixie Cron, as well as from the classic
94SVR3 syntax.
140.Sh AUTHORS
141.An Paul Vixie Aq paul@vix.com
95.SH DIAGNOSTICS
96A fairly informative usage message appears if you run it with a bad command
97line.
98.SH AUTHOR
99.nf
100Paul Vixie <paul@vix.com>