Manual page for crontab(1)
crontab - user crontab file
SYNOPSIS
crontab
[
filename
]
crontab [-elr] username
AVAILABILITY
SUNWcsu
DESCRIPTION
crontab
manages a user's access with
cron
by copying, creating, listing, and removing
crontab
files. If invoked without options,
crontab
copies the specified file,
or the standard input if no file is specified,
into a directory that holds all users' crontabs.
crontab Access Control
Users: Access to
crontab
is allowed:
-
- if the user's name appears in
/etc/cron.d/cron.allow.
- if
/etc/cron.d/cron.allow
does not exist and the user's name is not in
/etc/cron.d/cron.deny.
Users: Access to
crontab
is denied:
-
- if
/etc/cron.d/cron.allow
exists and the user's name is not in it.
- if
/etc/cron.d/cron.allow
does not exist and user's name is in
/etc/cron.d/cron.deny.
- if neither file exists.
Note that the rules for
allow
and
deny
apply to
root
only if the
allow/deny
files exist.
The
allow/deny
files consist of one user name per line.
crontab Entry Format
A
crontab
file consists of lines of six fields each.
The fields are separated by spaces or tabs.
The first five are integer patterns that
specify the following:
-
minute (0-59),
hour (0-23),
day of the month (1-31),
month of the year (1-12),
day of the week (0-6 with 0=Sunday).
Each of these patterns may
be either an asterisk (meaning all legal values)
or a list of elements separated by commas.
An element is either a number or
two numbers separated by a minus sign
(meaning an inclusive range).
Note that the specification of days
may be made by two fields
(day of the month and day of the week).
Both are adhered to if specified as a list of elements. See
EXAMPLES.
The sixth field of a line in a
crontab
file is a string that is executed by the shell
at the specified times.
A percent character
in this field (unless escaped by
\)
is translated to a NEWLINE
character.
Only the first line (up to a `%' or end of line) of
the command field is executed by the shell.
Other lines are made available to the command as standard input.
Any line beginning with a `#' is a comment and will be ignored.
The file should not contain blank lines.
The shell is invoked from your
$HOME
directory with an
arg0 of sh.
Users who desire to have their .profile executed must
explicitly do so in the
crontab
file.
cron
supplies a default environment for every shell, defining
HOME, LOGNAME,
SHELL(=/bin/sh), TZ, and
PATH.
The default PATH for
user
cron jobs is
/usr/bin;
while
root
cron jobs default to
/usr/sbin:/usr/bin.
The default PATH
can be set in
/etc/default/cron;
see
cron.1m
If you do not redirect the standard output
and standard error of your commands,
any generated output or errors
will be mailed to you.
OPTIONS
- -e
-
edits a copy of the current user's
crontab
file, or creates an empty file to edit if
crontab
does not exist.
When editing is complete, the file is installed as the user's
crontab
file.
If a
username
is given, the specified user's
crontab
file is edited, rather than the current user's
crontab
file;
this may only be done by a super-user.
The environment variable
EDITOR
determines which editor
is invoked with the
-e
option.
The default editor is
ed.1
Note that
all crontab jobs should be submitted using
crontab;
you should not add jobs by just editing the
crontab
file because
cron
will not be aware of changes made this way.
- -l
-
lists the
crontab
file for the invoking user. Only a super-user can specify a
username
following the
-r
or
-l
options to remove or list the
crontab
file
of the specified user.
- -r
-
removes a user's crontab from the crontab directory.
EXAMPLES
- 1.
-
Clean up
core
files every weekday morning at 3:15 am:
-
15 3 * * 1-5 find $HOME -name core 2>/dev/null | xargs rm -f
- 2.
-
Mail a birthday greeting:
-
0 12 14 2 * mailx john%Happy Birthday!%Time for lunch.
- 3.
-
As an example of specifying the two types of days:
-
0 0 1,15 * 1
-
would run a command on the
first and fifteenth of each month, as well as on every Monday.
To specify days by only one field,
the other field should be set to *, for example:
-
0 0 * * 1
-
would run a command only on Mondays.
ENVIRONMENT
See
environ.5
for descriptions of the following environment variables that
affect the execution of
crontab:
LC_TYPE,
LC_MESSAGES,
and
NLSPATH.
- EDITOR
-
Determine the editor to be invoked when the
-e
option is specified. The default editor is
ed.1
EXIT STATUS
The following exit values are returned:
- 0
-
Successful completion.
- >0
-
An error occurred.
FILES
- /etc/cron.d
-
main cron directory
- /etc/cron.d/cron.allow
-
list of allowed users
- /etc/default/cron
-
contains cron default settings
- /etc/cron.d/cron.deny
-
list of denied users
- /var/cron/log
-
accounting information
- /var/spool/cron/crontabs
-
spool area for
crontab.
SEE ALSO
atq.1
atrm.1
ed.1
sh.1
cron.1m
su.1m
environ.5
NOTES
If you inadvertently enter the
crontab
command with no argument(s), do not attempt to get out with
CTRL-D.
This removes all entries in your
crontab
file.
Instead, exit with
CTRL-C.
If a super-user modifies another user's crontab file, resulting
behavior may be unpredictable.
Instead, the privileged user
should first
su.1m
to the other user's login before making
any changes to the
crontab
file.
Created by unroff & hp-tools.
© by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97