386BSD 0.1 development
[unix-history] / usr / src / usr.bin / crontab / crontab.1
CommitLineData
33ee458a
WJ
1.\" $Header: crontab.1,v 2.1 90/07/18 00:23:43 vixie Exp $
2.\"
3.\"/* Copyright 1988,1990 by Paul Vixie
4.\" * All rights reserved
5.\" *
6.\" * Distribute freely, except: don't remove my name from the source or
7.\" * documentation (don't take credit for my work), mark your changes (don't
8.\" * get me blamed for your possible bugs), don't alter or remove this
9.\" * notice. May be sold if buildable source is provided to buyer. No
10.\" * warrantee of any kind, express or implied, is included with this
11.\" * software; use at your own risk, responsibility for damages (if any) to
12.\" * anyone resulting from the use of this software rests entirely with the
13.\" * user.
14.\" *
15.\" * Send bug reports, bug fixes, enhancements, requests, flames, etc., and
16.\" * I'll try to keep a version up to date. I can be reached as follows:
17.\" * Paul Vixie, 329 Noe Street, San Francisco, CA, 94114, (415) 864-7013,
18.\" * paul@vixie.sf.ca.us || {hoptoad,pacbell,decwrl,crash}!vixie!paul
19.\" */
20.TH CRONTAB 1 "9 December 1988"
21.UC 4
22.SH NAME
23crontab \- maintain crontab files for individual users
24.SH SYNOPSIS
25crontab [ -u user ] { -l | -d | -r file }
26.SH DESCRIPTION
27.I Crontab
28is the program used to install, deinstall or list the tables
29used to drive the
30.IR crond (8)
31daemon in Vixie Cron. Each user has their own crontab, and though these are
32files in /var, they are not readable or writable by anyone or anything
33except the super-user or the
34.IR crond (8)
35or
36.I crontab
37programs.
38.PP
39If the
40.I allow
41file exists, then you must be listed therein in order to be allowed to use
42this command. If the
43.I allow
44file does not exist but the
45.I deny
46file does exist, then you must \fBnot\fR be listed in the
47.I deny
48file in order to use this command. If neither of these files exists, then
49depending on site-dependent configuration parameters, only the super user
50will be allowed to use this command, or all users will be able to use this
51command.
52.PP
53If the
54.I -u
55option is given, it specifies the name of the user whose crontab is to be
56tweaked. If this option is not given,
57.I crontab
58examines "your" crontab, i.e., the crontab of the person executing the
59command. Note that
60.IR su (8)
61can confuse
62.I crontab
63and that if you are running inside of
64.IR su (8)
65you should always use the
66.I -u
67option for safety's sake.
68.PP
69The
70.I -l
71option causes the current crontab to be displayed on standard output.
72.PP
73The
74.I -d
75option causes the current crontab to be deleted.
76.PP
77The
78.I -r
79option is used to replace the current
80crontab (if any) with the contents of the named file.
81.SH "SEE ALSO"
82crontab(5), crond(8)
83.SH FILES
84.nf
85/var/cron/allow
86/var/cron/deny
87.fi
88.SH DIAGNOSTICS
89A fairly informative usage message appears if you run it with a bad command
90line.
91.SH AUTHOR
92.nf
93Paul Vixie, paul@vixie.sf.ca.us