Create correct man pages in man directory.
Add .gitignore file.
--- /dev/null
+Makefile.in
+Makefile
+aclocal.m4
+autom4te.cache
+config.guess
+config.h
+config.h.in
+config.log
+config.status
+config.sub
+configure
+depcomp
+install-sh
+missing
+stamp-h1
+.deps
+*.o
+src/crond
+src/crontab
+*~
+*.tar.*
if PAM
pamdir = $(sysconfdir)/pam.d
-dist_pam_DATA = crond.pam
+dist_pam_DATA = pam/crond
endif
#config_DATA = crond.sysconfig
--- /dev/null
+.\" Copyright (c) 1989, 1991, 1993
+.\" The Regents of the University of California. All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" Paul Vixie.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\" notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\" notice, this list of conditions and the following disclaimer in the
+.\" documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\" must display the following acknowledgement:
+.\" This product includes software developed by the University of
+.\" California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\" may be used to endorse or promote products derived from this software
+.\" without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\" @(#)bitstring.3 8.1 (Berkeley) 7/19/93
+.\"
+.TH BITSTRING 3 "July 19, 1993"
+.SH NAME
+\fBbit_alloc\fP,
+\fBbit_clear\fP,
+\fBbit_decl\fP,
+\fBbit_ffs\fP,
+\fBbit_nclear\fP,
+\fBbit_nset,\fP
+\fBbit_set\fP,
+\fBbitstr_size\fP,
+\fBbit_test\fP
+\- bit-string manipulation macros
+.SH SYNOPSIS
+.nf
+\fB#include <bitstring.h>\fP
+
+\f2bitstr_t\f1 \f2*\f1
+\fBbit_alloc\fP(\f2int\f1 \f2nbits\f1);
+
+\fBbit_decl\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2nbits\f1);
+
+\fBbit_clear\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2bit\f1);
+
+\fBbit_ffc\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2nbits\f1, \f2int\f1 \f2*value\f1);
+
+\fBbit_ffs\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2nbits\f1, \f2int\f1 \f2*value\f1);
+
+\fBbit_nclear\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2start\f1, \f2int\f1 \f2stop\f1);
+
+\fBbit_nset\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2start\f1, \f2int\f1 \f2stop\f1);
+
+\fBbit_set\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2bit\f1);
+
+\fBbitstr_size\fP(\f2int\f1 \f2nbits\f1);
+
+\fBbit_test\fP(\f2bit_str\f1 \f2name\f1, \f2int\f1 \f2bit\f1);
+.fi
+.SH DESCRIPTION
+These macros operate on strings of bits.
+.PP
+The macro \fBbit_alloc\fP() returns a pointer of type
+``\f2bitstr_t\f1 \f2*\f1'' to sufficient space to store
+.I nbits
+bits, or NULL if no space is available.
+.PP
+The macro \fBbit_decl\fP() allocates sufficient space to store
+.I nbits
+bits on the stack.
+.PP
+The macro \fBbitstr_size\fP() returns the number of elements of type
+.I bitstr_t
+necessary to store
+.I nbits
+bits.
+This is useful for copying bit strings.
+.PP
+The macros
+\fBbit_clear\fP()
+and
+\fBbit_set\fP()
+clear or set the zero-based numbered bit
+.IR bit ,
+in the bit string
+.IR name .
+.PP
+The
+\fBbit_nset\fP()
+and
+\fBbit_nclear\fP()
+macros set or clear the zero-based numbered bits from
+.I start
+to
+.I stop
+in the bit string
+.IR name .
+.PP
+The
+\fBbit_test\fP() macro evaluates to non-zero if the zero-based numbered bit
+.I bit
+of bit string
+.I name
+is set, and zero otherwise.
+.PP
+The \fBbit_ffs\fP() macro stores in the location referenced by
+.I value
+the zero-based number of the first bit set in the array of
+.I nbits
+bits referenced by
+.IR name .
+If no bits are set, the location referenced by
+.I value
+is set to \-1.
+.PP
+The macro \fBbit_ffc\fP() stores in the location referenced by
+.I value
+the zero-based number of the first bit not set in the array of
+.I nbits
+bits referenced by
+.IR name .
+If all bits are set, the location referenced by
+.I value
+is set to \-1.
+.PP
+The arguments to these macros are evaluated only once and may safely
+have side effects.
+.SH EXAMPLE
+.nf
+.in +5
+#include <limits.h>
+#include <bitstring.h>
+
+#define LPR_BUSY_BIT 0
+#define LPR_FORMAT_BIT 1
+#define LPR_DOWNLOAD_BIT 2
+#define LPR_AVAILABLE_BIT 9
+#define LPR_MAX_BITS 10
+
+make_lpr_available()
+{
+ bitstr_t bit_decl(bitlist, LPR_MAX_BITS);
+ ...
+ bit_nclear(bitlist, 0, LPR_MAX_BITS - 1);
+ ...
+ if (!bit_test(bitlist, LPR_BUSY_BIT)) {
+ bit_clear(bitlist, LPR_FORMAT_BIT);
+ bit_clear(bitlist, LPR_DOWNLOAD_BIT);
+ bit_set(bitlist, LPR_AVAILABLE_BIT);
+ }
+}
+.fi
+.SH SEE ALSO
+malloc(3)
--- /dev/null
+.\"/* Copyright 1988,1990,1993,1996 by Paul Vixie
+.\" * All rights reserved
+.\" */
+.\"
+.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
+.\" Copyright (c) 1997,2000 by Internet Software Consortium, Inc.
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+.\" OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.\" $Id: cron.8,v 1.8 2004/01/23 19:03:32 vixie Exp $
+.\"
+.TH CRON "8" "10 January 2007" "Linux Programmer's Manual"
+.UC 4
+.SH NAME
+cron \- daemon to execute scheduled commands (ISC Cron V4.1)
+.SH SYNOPSIS
+.B cron
+.RB [ -n " | " -p " | " -m \fP\fI<mail command>\fP\fB ]
+.br
+.B cron
+.B -x
+.RB [ext,sch,proc,pars,load,misc,test,bit]
+.br
+.SH DESCRIPTION
+.I Cron
+should be started from
+.I /etc/rc.d/init.d
+or
+.I /etc/init.d
+. It will return immediately, so you don't need to start it with '&'.
+.PP
+.I Cron
+searches
+.I /var/spool/cron
+for crontab files which are named after accounts in
+.I/etc/passwd;
+crontabs found are loaded into memory.
+.I Cron
+also searches for
+.I /etc/crontab
+and the files in the
+.I/etc/cron.d
+directory, which are in a different format (see
+.BR crontab (5)
+).
+.I Cron
+then wakes up every minute, examining all stored crontabs, checking each
+command to see if it should be run in the current minute. When executing
+commands, any output is mailed to the owner of the crontab (or to the user
+named in the MAILTO environment variable in the crontab, if such exists).
+.PP
+Additionally,
+.I cron
+checks each minute to see if its spool directory's modtime (or the modtime
+on
+.IR /etc/crontab )
+has changed, and if it has,
+.I cron
+will then examine the modtime on all crontabs and reload those which have
+changed. Thus
+.I cron
+need not be restarted whenever a crontab file is modified. Note that the
+.BR crontab (1)
+command updates the modtime of the spool directory whenever it changes a
+crontab.
+.PP
+.SS Daylight Saving Time and other time changes
+Local time changes of less than three hours, such as those caused
+by the start or end of Daylight Saving Time, are handled specially.
+This only applies to jobs that run at a specific time and jobs that
+are run with a granularity greater than one hour. Jobs that run
+more frequently are scheduled normally.
+.PP
+If time has moved forward, those jobs that would have run in the
+interval that has been skipped will be run immediately.
+Conversely, if time has moved backward, care is taken to avoid running
+jobs twice.
+.PP
+Time changes of more than 3 hours are considered to be corrections to
+the clock or timezone, and the new time is used immediately.
+.PP
+It's possible to use different time zones for cron tables. More could
+be found in
+.IR crontab (5).
+.SS PAM Access Control
+On Red Hat systems, crond now supports access control with PAM - see
+.IR pam (8).
+A PAM configuration file for crond is installed in /etc/pam.d/crond.
+crond loads the PAM environment from the pam_env module, but these
+can be overriden by settings in the crontab file.
+.SH "OPTIONS"
+.TP
+.B "\-m"
+This option allows you to specify a shell command string to use for sending cron mail
+output instead of
+.BR sendmail (8).
+This command must accept a fully formatted mail message (with headers) on stdin and send it
+as a mail message to the recipients specified in the mail headers.
+.TP
+.B "\-n"
+This option changes default behavior causing it to run crond in the foreground. This can be
+useful when starting it out of init.
+.TP
+.B "\-p"
+Cron permit any crontab, which user set.
+.TP
+.B "\-x"
+With this option is possible to set debug flags.
+.SH SIGNALS
+On receipt of a \s-2SIGHUP\s+2, the cron daemon will close and reopen its
+log file. This is useful in scripts which rotate and age log files.
+Naturally this is not relevant if cron was built to use
+.IR syslog (3).
+.SH CAVEATS
+In this version of
+.BR cron
+, without the \fB-p\fP option,
+.I /etc/crontab
+must not be writable by any user other than root,
+no crontab files may be links, or linked to by any other file,
+and no crontab files may be executable, or be writable by any
+user other than their owner.
+.SH "SEE ALSO"
+.IR crontab (1),
+.IR crontab (5),
+.IR pam (8)
+.SH AUTHOR
+.nf
+Paul Vixie <vixie@isc.org>
--- /dev/null
+.\"/* Copyright 1988,1990,1993 by Paul Vixie
+.\" * All rights reserved
+.\" */
+.\"
+.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
+.\" Copyright (c) 1997,2000 by Internet Software Consortium, Inc.
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+.\" OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.\" $Id: crontab.1,v 1.7 2004/01/23 19:03:32 vixie Exp $
+.\"
+.TH CRONTAB 1 "27 July 2007"
+.UC 4
+.SH NAME
+crontab \- maintain crontab files for individual users (ISC Cron V4.1)
+.SH SYNOPSIS
+.B crontab
+.RB [ -u
+.IR user ] " file"
+.br
+.B crontab
+.RB [ -u
+.IR user ]
+.RB [ -l " | " -r " | " -e ]\ [ -i ]
+.RB [ -s ]
+.SH DESCRIPTION
+.I Crontab
+is the program used to install, deinstall or list the tables
+used to drive the
+.BR cron (8)
+daemon in ISC Cron. Each user can have their own crontab, and though these are files in
+.I /var/spool/
+, they are not intended to be edited directly. For SELinux in mls mode can be even
+more crontabs - for each range. For more see
+.BR selinux (8).
+.PP
+The cron jobs could be allow or disallow for different users. For classical
+crontab there exists
+.I cron.allow
+and
+.I cron.deny
+files.
+If
+.I cron.allow
+file exists, then you must be listed therein in order to be allowed to use
+this command. If the
+.I cron.allow
+file does not exist but the
+.I cron.deny
+file does exist, then you must \fInot\fR be listed in the
+.I cron.deny
+file in order to use this command. If neither of these files exists,
+only the super user will be allowed to use this command.
+The second option is using PAM authentication, where you set up users,
+which could or couldn't use
+.I crontab
+and \fBalso\fR system cron jobs from
+/etc/cron.d/.
+.PP
+.SH "OPTIONS"
+.TP
+.B "\-u"
+Append the name of the user whose crontab is to be tweaked. If this option
+is not given,
+.I crontab
+examines "your" crontab, i.e., the crontab of the person executing the
+command. Note that
+.BR su (8)
+can confuse
+.I crontab
+and that if you are running inside of
+.BR su (8)
+you should always use the
+.B -u
+option for safety's sake.
+The first form of this command is used to install a new crontab from some
+named file or standard input if the pseudo-filename "-" is given.
+.TP
+.B "\-l"
+The current crontab will be displayed on standard output.
+.TP
+.B "\-r"
+The current crontab will be be removed.
+.TP
+.B "\-e"
+This option is used to edit the current crontab using the editor specified by
+the \s-1VISUAL\s+1 or \s-1EDITOR\s+1 environment variables. After you exit
+from the editor, the modified crontab will be installed automatically.
+.TP
+.B "\-i"
+This option modifies the
+.B "\-r"
+option to prompt the user for a 'y/Y' response
+before actually removing the crontab.
+.TP
+.B "\-s"
+It will append the current SELinux security context string as an
+MLS_LEVEL setting to the crontab file before editing / replacement
+occurs - see the documentation of MLS_LEVEL in
+.BR crontab(5)\.
+.SH "SEE ALSO"
+crontab(5), cron(8)
+.SH FILES
+.nf
+/etc/cron.allow
+/etc/cron.deny
+.fi
+.SH STANDARDS
+The
+.I crontab
+command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax
+differs from previous versions of Vixie Cron, as well as from the classic
+SVR3 syntax.
+.SH DIAGNOSTICS
+A fairly informative usage message appears if you run it with a bad command
+line.
+.SH AUTHOR
+.nf
+Paul Vixie <vixie@isc.org>
--- /dev/null
+.\"/* Copyright 1988,1990,1993,1994 by Paul Vixie
+.\" * All rights reserved
+.\" */
+.\"
+.\" Copyright (c) 2004 by Internet Systems Consortium, Inc. ("ISC")
+.\" Copyright (c) 1997,2000 by Internet Software Consortium, Inc.
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+.\" OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.\" $Id: crontab.5,v 1.6 2004/01/23 19:03:33 vixie Exp $
+.\"
+.TH CRONTAB 5 "27 July 2007"
+.UC 4
+.SH NAME
+crontab \- tables for driving cron (ISC Cron V4.1)
+.SH DESCRIPTION
+A
+.I crontab
+file contains instructions to the
+.BR cron (8)
+daemon of the general form: "run this command at this time on this date".
+Each user has their own crontab, and commands in any given crontab will be
+executed as the user who owns the crontab. Uucp and News will usually have
+their own crontabs, eliminating the need for explicitly running
+.BR su (1)
+as part of a cron command.
+.PP
+Blank lines and leading spaces and tabs are ignored. Lines whose first
+non-space character is a pound-sign (#) are comments, and are ignored.
+Note that comments are not allowed on the same line as cron commands, since
+they will be taken to be part of the command. Similarly, comments are not
+allowed on the same line as environment variable settings.
+.PP
+An active line in a crontab will be either an environment setting or a cron
+command. An environment setting is of the form,
+.PP
+ name = value
+.PP
+where the spaces around the equal-sign (=) are optional, and any subsequent
+non-leading spaces in
+.I value
+will be part of the value assigned to
+.IR name .
+The
+.I value
+string may be placed in quotes (single or double, but matching) to preserve
+leading or trailing blanks.
+.PP
+Several environment variables are set up
+automatically by the
+.BR cron (8)
+daemon.
+SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd
+line of the crontab\'s owner.
+HOME and SHELL may be overridden by settings in the crontab; LOGNAME may not.
+.PP
+(Another note: the LOGNAME variable is sometimes called USER on BSD systems...
+on these systems, USER will be set also.)
+.PP
+In addition to LOGNAME, HOME, and SHELL,
+.BR cron (8)
+will look at MAILTO if it has any reason to send mail as a result of running
+commands in "this" crontab. If MAILTO is defined (and non-empty), mail is
+sent to the user so named. If MAILTO is defined but empty (MAILTO=""), no
+mail will be sent. Otherwise mail is sent to the owner of the crontab. This
+option is useful if you decide on /bin/mail instead of /usr/lib/sendmail as
+your mailer when you install cron -- /bin/mail doesn\'t do aliasing, and UUCP
+usually doesn\'t read its mail.
+.PP
+By default, cron will send mail using the mail 'Content-Type:' header of 'text/plain'
+with the 'charset=' parameter set to the charmap / codeset of the locale in which
+.BR crond (8)
+is started up - ie. either the default system locale, if no LC_* environment
+variables are set, or the locale specified by the LC_* environment variables
+(see
+.BR locale (7)).
+You can use different character encodings for mailed cron job output by
+setting the CONTENT_TYPE and CONTENT_TRANSFER_ENCODING variables in crontabs,
+to the correct values of the mail headers of those names.
+.PP
+The CRON_TZ specifies the time zone specific for the cron table. User type into
+the chosen table times in the time of the specified time zone. The time into log
+is taken from local time zone, where is the daemon running.
+.PP
+The MLS_LEVEL environment variable provides support for multiple per-job
+SELinux security contexts in the same crontab.
+By default, cron jobs execute with the default SELinux security context of the
+user that created the crontab file.
+When using multiple security levels and roles, this may not be sufficient, because
+the same user may be running in a different role or at a different security level.
+For more about roles and SELinux MLS/MCS see
+.BR selinux (8)
+and undermentioned crontab example.
+You can set MLS_LEVEL to the SELinux security context string specifying
+the SELinux security context in which you want the job to run, and crond will set
+the execution context of the or jobs to which the setting applies to the specified
+context.
+See also the
+.BR crontab(1)\ -s\ option.
+.PP
+The format of a cron command is very much the V7 standard, with a number of
+upward-compatible extensions. Each line has five time and date fields,
+followed by a user name if this is the system crontab file,
+followed by a command. Commands are executed by
+.BR cron (8)
+when the minute, hour, and month of year fields match the current time,
+.I and
+at least one of the two day fields (day of month, or day of week)
+match the current time (see "Note" below).
+Note that this means that non-existent times, such as "missing hours"
+during daylight savings conversion, will never match, causing jobs
+scheduled during the "missing times" not to be run. Similarly, times
+that occur more than once (again, during daylight savings conversion)
+will cause matching jobs to be run twice.
+.PP
+.BR cron (8)
+examines cron entries once every minute.
+.PP
+The time and date fields are:
+.IP
+.ta 1.5i
+field allowed values
+.br
+----- --------------
+.br
+minute 0-59
+.br
+hour 0-23
+.br
+day of month 1-31
+.br
+month 1-12 (or names, see below)
+.br
+day of week 0-7 (0 or 7 is Sun, or use names)
+.br
+.PP
+A field may be an asterisk (*), which always stands for "first\-last".
+.PP
+Ranges of numbers are allowed. Ranges are two numbers separated
+with a hyphen. The specified range is inclusive. For example,
+8-11 for an "hours" entry specifies execution at hours 8, 9, 10
+and 11.
+.PP
+Lists are allowed. A list is a set of numbers (or ranges)
+separated by commas. Examples: "1,2,5,9", "0-4,8-12".
+.PP
+Step values can be used in conjunction with ranges. Following
+a range with "<number>" specifies skips of the number's value
+through the range. For example, "0-23/2" can be used in the hours
+field to specify command execution every other hour (the alternative
+in the V7 standard is "0,2,4,6,8,10,12,14,16,18,20,22"). Steps are
+also permitted after an asterisk, so if you want to say "every two
+hours", just use "*/2".
+.PP
+Names can also be used for the "month" and "day of week"
+fields. Use the first three letters of the particular
+day or month (case doesn't matter). Ranges or
+lists of names are not allowed.
+.PP
+The "sixth" field (the rest of the line) specifies the command to be
+run.
+The entire command portion of the line, up to a newline or %
+character, will be executed by /bin/sh or by the shell
+specified in the SHELL variable of the cronfile.
+Percent-signs (%) in the command, unless escaped with backslash
+(\\), will be changed into newline characters, and all data
+after the first % will be sent to the command as standard
+input.
+.PP
+Note: The day of a command's execution can be specified by two
+fields \(em day of month, and day of week. If both fields are
+restricted (ie, aren't *), the command will be run when
+.I either
+field matches the current time. For example,
+.br
+"30 4 1,15 * 5"
+would cause a command to be run at 4:30 am on the 1st and 15th of each
+month, plus every Friday.
+.SH EXAMPLE CRON FILE
+.nf
+# use /bin/sh to run commands, no matter what /etc/passwd says
+SHELL=/bin/sh
+# mail any output to `paul', no matter whose crontab this is
+MAILTO=paul
+#
+CRON_TZ=Japan
+# run five minutes after midnight, every day
+5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
+# run at 2:15pm on the first of every month -- output mailed to paul
+15 14 1 * * $HOME/bin/monthly
+# run at 10 pm on weekdays, annoy Joe
+0 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?%
+23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday"
+5 4 * * sun echo "run at 5 after 4 every sunday"
+.fi
+.SH Jobs in /etc/cron.d/
+The jobs in cron.d are system jobs, which are used usually for more than
+one user. That's the reason why is name of the user needed. MAILTO on the first line
+is optional.
+.SH EXAMPLE FOR JOB IN /etc/cron.d/job
+.nf
+#login as root
+#create job with preferred editor (e.g. vim)
+MAILTO=root
+* * * * * root touch /tmp/file
+.fi
+.SH SELinux with multi level security (MLS)
+In crontab is important specified security level by \fIcrontab\ -s\fR or specifying
+the required level on the first line of the crontab. Each level is specified
+in \fI/etc/selinux/targeted/seusers\fR. For using crontab in MLS mode is really important:
+.br
+- check/change actual role,
+.br
+- set correct \fIrole for directory\fR, which is used for input/output.
+.SH EXAMPLE FOR SELINUX MLS
+.nf
+# login as root
+newrole -r sysadm_r
+mkdir /tmp/SystemHigh
+chcon -l SystemHigh /tmp/SystemHigh
+crontab -e
+# write in crontab file
+MLS_LEVEL=SystemHigh
+0-59 * * * * id -Z > /tmp/SystemHigh/crontest
+When I log in as a normal user, it can't work, because \fI/tmp/SystemHigh\fR is
+higher than my level.
+.fi
+.SH FILES
+.I /etc/crontab
+system crontab file
+.SH "SEE ALSO"
+.BR cron (8),
+.BR crontab (1)
+.SH EXTENSIONS
+When specifying day of week, both day 0 and day 7 will be considered Sunday.
+BSD and ATT seem to disagree about this.
+.PP
+Lists and ranges are allowed to co-exist in the same field. "1-3,7-9" would
+be rejected by ATT or BSD cron -- they want to see "1-3" or "7,8,9" ONLY.
+.PP
+Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
+.PP
+Names of months or days of the week can be specified by name.
+.PP
+Environment variables can be set in the crontab. In BSD or ATT, the
+environment handed to child processes is basically the one from /etc/rc.
+.PP
+Command output is mailed to the crontab owner (BSD can't do this), can be
+mailed to a person other than the crontab owner (SysV can't do this), or the
+feature can be turned off and no mail will be sent at all (SysV can't do this
+either).
+.PP
+These special time specification "nicknames" are supported, which replace
+the 5 initial time and date fields, and are prefixed by the '@' character:
+.nf
+@reboot : Run once, at startup.
+@yearly : Run once a year, ie. "0 0 1 1 *".
+@annually : Run once a year, ie. "0 0 1 1 *".
+@monthly : Run once a month, ie. "0 0 1 * *".
+@weekly : Run once a week, ie. "0 0 * * 0".
+@daily : Run once a day, ie. "0 0 * * *".
+@hourly : Run once an hour, ie. "0 * * * *".
+.fi
+.SH CAVEATS
+In this version of
+.I cron
+,
+.I /etc/crontab
+must not be writable by any user other than root.
+No crontab files may be links, or linked to by any other file.
+No crontab files may be executable, or be writable by any user
+other than their owner.
+.SH AUTHOR
+.nf
+Paul Vixie <vixie@isc.org>
projects / cronie / commitdiff