1) Added s/key support .
[unix-history] / usr.bin / crontab / crontab.1
CommitLineData
693d8207 1.\"/* Copyright 1988,1990,1993 by Paul Vixie
15637ed4
RG
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:
693d8207 15.\" * Paul Vixie <paul@vix.com> uunet!decwrl!vixie!paul
15637ed4 16.\" */
693d8207
GR
17.\"
18.\" $Header: $
19.\"
20.\" From Id: crontab.1,v 2.4 1993/12/31 10:47:33 vixie Exp
21.\"
22.TH CRONTAB 1 "29 December 1993"
15637ed4
RG
23.UC 4
24.SH NAME
693d8207 25crontab \- maintain crontab files for individual users (V3)
15637ed4 26.SH SYNOPSIS
693d8207
GR
27crontab [ -u user ] file
28.br
29crontab [ -u user ] { -l | -r | -e }
15637ed4
RG
30.SH DESCRIPTION
31.I Crontab
32is the program used to install, deinstall or list the tables
33used to drive the
693d8207
GR
34.IR cron (8)
35daemon in Vixie Cron. Each user can have their own crontab, and though
36these are files in /var, they are not intended to be edited directly.
15637ed4
RG
37.PP
38If the
39.I allow
40file exists, then you must be listed therein in order to be allowed to use
41this command. If the
42.I allow
43file does not exist but the
44.I deny
45file does exist, then you must \fBnot\fR be listed in the
46.I deny
47file in order to use this command. If neither of these files exists, then
48depending on site-dependent configuration parameters, only the super user
49will be allowed to use this command, or all users will be able to use this
50command.
51.PP
52If the
53.I -u
54option is given, it specifies the name of the user whose crontab is to be
55tweaked. If this option is not given,
56.I crontab
57examines "your" crontab, i.e., the crontab of the person executing the
58command. Note that
59.IR su (8)
60can confuse
61.I crontab
62and that if you are running inside of
63.IR su (8)
64you should always use the
65.I -u
66option for safety's sake.
67.PP
693d8207
GR
68The first form of this command is used to install a new crontab from some
69named file or standard input if the pseudo-filename ``-'' is given.
70.PP
15637ed4
RG
71The
72.I -l
73option causes the current crontab to be displayed on standard output.
74.PP
75The
693d8207
GR
76.I -r
77option causes the current crontab to be removed.
15637ed4
RG
78.PP
79The
693d8207
GR
80.I -e
81option is used to edit the current crontab using the editor specified by
82the \s-1VISUAL\s+1 or \s-1EDITOR\s+1 environment variables. After you exit
83from the editor, the modified crontab will be installed automatically.
15637ed4 84.SH "SEE ALSO"
693d8207 85crontab(5), cron(8)
15637ed4
RG
86.SH FILES
87.nf
88/var/cron/allow
89/var/cron/deny
90.fi
693d8207
GR
91.SH STANDARDS
92The
93.I crontab
94command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax
95differs from previous versions of Vixie Cron, as well as from the classic
96SVR3 syntax.
15637ed4
RG
97.SH DIAGNOSTICS
98A fairly informative usage message appears if you run it with a bad command
99line.
100.SH AUTHOR
101.nf
693d8207 102Paul Vixie <paul@vix.com>