crontab.1 (476602a9d0b9041b42a108349dc58a4ca6bf4223) crontab.1 (401e64688be376d8c5cdae5d0e2b4bf14e88ac15)
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.\" $Id$
18.\" $Id: crontab.1,v 1.3 1997/02/22 16:04:51 peter Exp $
19.\"
19.\"
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
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 crontab
28.Op Fl u Ar user
29.Ar file
30.Nm crontab
31.Op Fl u Ar user
32{
33.Fl l |
34.Fl r |
35.Fl e
36}
37.Sh DESCRIPTION
38.Nm Crontab
30is the program used to install, deinstall or list the tables
31used to drive the
39is the program used to install, deinstall or list the tables
40used to drive the
32.IR cron (8)
41.Xr cron 8
33daemon in Vixie Cron. Each user can have their own crontab, and though
42daemon 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
43these are files in
44.Pa /var ,
45they are not intended to be edited directly.
46.Pp
36If the
47If the
37.I allow
48.Pa allow
38file exists, then you must be listed therein in order to be allowed to use
39this command. If the
49file exists, then you must be listed therein in order to be allowed to use
50this command. If the
40.I allow
51.Pa allow
41file does not exist but the
52file does not exist but the
42.I deny
43file does exist, then you must \fBnot\fR be listed in the
44.I deny
53.Pa deny
54file does exist, then you must
55.Em not
56be listed in the
57.Pa deny
45file in order to use this command. If neither of these files exists, then
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.
58file in order to use this command. If neither of these files exists, then
59depending on site-dependent configuration parameters, only the super user
60will be allowed to use this command, or all users will be able to use this
61command.
49.PP
50If the
51.I -u
52option is given, it specifies the name of the user whose crontab is to be
62.Pp
63The first form of this command is used to install a new crontab from some
64named file or standard input if the pseudo-filename ``-'' is given.
65.Pp
66The following options are available:
67.Bl -tag -width indent
68.It Fl u
69Specify the name of the user whose crontab is to be
53tweaked. If this option is not given,
70tweaked. If this option is not given,
54.I crontab
71.Nm
55examines "your" crontab, i.e., the crontab of the person executing the
56command. Note that
72examines "your" crontab, i.e., the crontab of the person executing the
73command. Note that
57.IR su (8)
74.Xr su 8
58can confuse
75can confuse
59.I crontab
76.Nm
60and that if you are running inside of
77and that if you are running inside of
61.IR su (8)
78.Xr su 8
62you should always use the
79you should always use the
63.I -u
80.Fl u
64option for safety's sake.
81option for safety's sake.
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
82.It Fl l
83Display the current crontab on standard output.
84.It Fl r
85Remove the current crontab.
86.It Fl e
87Edit the current crontab using the editor specified by
88the
89.Ev VISUAL
90or
91.Ev EDITOR
92environment variables. After you exit
81from the editor, the modified crontab will be installed automatically.
93from the editor, the modified crontab will be installed automatically.
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
94.El
95.Sh SEE ALSO
96.Xr crontab 5 ,
97.Xr cron 8
98.Sh FILES
99.Bl -tag -width /var/cron/allow -compact
100.It Pa /var/cron/allow
101.It Pa /var/cron/deny
102.El
103.Sh STANDARDS
90The
104The
91.I crontab
92command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax
105.Nm
106command conforms to
107.St -p1003.2 .
108This new command syntax
93differs from previous versions of Vixie Cron, as well as from the classic
94SVR3 syntax.
109differs from previous versions of Vixie Cron, as well as from the classic
110SVR3 syntax.
95.SH DIAGNOSTICS
111.Sh DIAGNOSTICS
96A fairly informative usage message appears if you run it with a bad command
97line.
112A fairly informative usage message appears if you run it with a bad command
113line.
98.SH AUTHOR
99.nf
100Paul Vixie <paul@vix.com>
114.Sh AUTHOR
115.An Paul Vixie Aq paul@vix.com