1CRONTAB(1)                       User Commands                      CRONTAB(1)
2
3
4

NAME

6       crontab - maintains crontab files for individual users
7

SYNOPSIS

9       crontab [-u user] file
10       crontab [-u user] [-l | -r | -e] [-i] [-s]
11       crontab -n [ hostname ]
12       crontab -c
13       crontab -V
14

DESCRIPTION

16       Crontab  is the program used to install a crontab table file, remove or
17       list the existing tables used to serve the cron(8) daemon.   Each  user
18       can  have their own crontab, and though these are files in /var/spool/,
19       they are not intended to be edited directly.  For SELinux in MLS  mode,
20       you can define more crontabs for each range.  For more information, see
21       selinux(8).
22
23       In this version of Cron it is possible to use a network-mounted  shared
24       /var/spool/cron  across a cluster of hosts and specify that only one of
25       the hosts should run the crontab jobs in the  particular  directory  at
26       any  one  time.  You may also use crontab(1) from any of these hosts to
27       edit the same shared set of crontab files, and to set and  query  which
28       host should run the crontab jobs.
29
30       Running  cron  jobs  can  be allowed or disallowed for different users.
31       For this purpose, use the  cron.allow  and  cron.deny  files.   If  the
32       cron.allow  file  exists,  a user must be listed in it to be allowed to
33       use cron If the cron.allow file does not exist but the  cron.deny  file
34       does  exist,  then  a  user must not be listed in the cron.deny file in
35       order to use cron.  If neither of these files exists,  only  the  super
36       user is allowed to use cron.  Another way to restrict access to cron is
37       to use PAM authentication in /etc/security/access.conf to set up users,
38       which  are  allowed  or disallowed to use crontab or modify system cron
39       jobs in the /etc/cron.d/ directory.
40
41       The temporary directory can be set in an environment variable.   If  it
42       is not set by the user, the /tmp directory is used.
43

OPTIONS

45       -u     Appends  the  name  of the user whose crontab is to be modified.
46              If this option is not used,  crontab  examines  "your"  crontab,
47              i.e.,  the  crontab  of  the person executing the command.  Note
48              that su(8) may confuse crontab, thus,  when  executing  commands
49              under  su(8) you should always use the -u option.  If no crontab
50              exists for a particular user, it is created for  him  the  first
51              time the crontab -u command is used under his username.
52
53       -l     Displays the current crontab on standard output.
54
55       -r     Removes the current crontab.
56
57       -e     Edits the current crontab using the editor specified by the VIS‐
58              UAL or EDITOR environment variables.  After you  exit  from  the
59              editor, the modified crontab will be installed automatically.
60
61       -i     This  option  modifies  the  -r  option to prompt the user for a
62              'y/Y' response before actually removing the crontab.
63
64       -s     Appends the  current  SELinux  security  context  string  as  an
65              MLS_LEVEL  setting to the crontab file before editing / replace‐
66              ment occurs - see the documentation of MLS_LEVEL in crontab(5).
67
68       -n     This option is relevant only if cron(8) was started with the  -c
69              option,  to  enable  clustering  support.  It is used to set the
70              host in the cluster which should run the jobs specified  in  the
71              crontab  files  in the /var/spool/cron directory.  If a hostname
72              is supplied, the host whose hostname returned by  gethostname(2)
73              matches  the  supplied  hostname,  will  be  selected to run the
74              selected cron jobs subsequently.  If there is  no  host  in  the
75              cluster  matching the supplied hostname, or you explicitly spec‐
76              ify an empty hostname, then the selected jobs will not be run at
77              all.   If  the  hostname  is omitted, the name of the local host
78              returned by gethostname(2) is used.  Using this  option  has  no
79              effect on the /etc/crontab file and the files in the /etc/cron.d
80              directory, which are always run, and  considered  host-specific.
81              For more information on clustering support, see cron(8).
82
83       -c     This  option is only relevant if cron(8) was started with the -c
84              option, to enable clustering support.  It is used to query which
85              host  in  the cluster is currently set to run the jobs specified
86              in the crontab files in the directory /var/spool/cron ,  as  set
87              using the -n option.
88
89       -V     Print version and exit.
90

SEE ALSO

92       crontab(5), cron(8)
93

FILES

95       /etc/cron.allow
96       /etc/cron.deny
97

STANDARDS

99       The  crontab command conforms to IEEE Std1003.2-1992 (``POSIX'').  This
100       new command syntax differs from previous versions  of  Vixie  Cron,  as
101       well as from the classic SVR3 syntax.
102

DIAGNOSTICS

104       An informative usage message appears if you run a crontab with a faulty
105       command defined in it.
106

AUTHOR

108       Paul Vixie ⟨vixie@isc.org⟩
109       Colin Dean ⟨colin@colin-dean.org⟩
110
111
112
113cronie                            2012-11-22                        CRONTAB(1)
Impressum