HardenedBSD/etc/crontab

# /etc/crontab - root's crontab for FreeBSD
#
# $FreeBSD$
#
SHELL=/bin/sh
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
HOME=/var/log
#
#minute	hour	mday	month	wday	who	command
#
# save some entropy so that /dev/random can reseed on boot
*/3	*	*	*	*	operator /usr/libexec/save-entropy
#
*/5	*	*	*	*	root	/usr/libexec/atrun
#
# rotate log files every hour, if necessary
0	*	*	*	*	root	newsyslog
#
# do daily/weekly/monthly maintenance
1	3	*	*	*	root	periodic daily
15	4	*	*	6	root	periodic weekly
30	5	1	*	*	root	periodic monthly
#
# time zone change adjustment for wall cmos clock,
# does nothing, if you have UTC cmos clock.
# See adjkerntz(8) for details.
1,31	0-5	*	*	*	root	adjkerntz -a
As a result of the distribution crontab, /usr/libexec/atrun was being run only once an hour instead of every five minutes. This was due to a minute specification of 0/5 -- which should have been */5. This has been fixed. Expect your /var/cron/log to grow much faster now. 1994-04-15 18:57:38 +02:00			`# /etc/crontab - root's crontab for FreeBSD`
Cleaned up crontab from NetBSD, adjusted for FreeBSD. 1993-07-19 21:08:04 +02:00			`#`
$Id$ -> $FreeBSD$ 1999-08-28 01:37:10 +02:00			`# $FreeBSD$`
Cleaned up crontab from NetBSD, adjusted for FreeBSD. 1993-07-19 21:08:04 +02:00			`#`
			`SHELL=/bin/sh`
			`PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin`
			`HOME=/var/log`
			`#`
This is Vixie cron 3.0. This version fixes all known security bugs. Further it implements crontab -e. I moved cron from /usr/libexec to /usr/sbin where most daemons are that are run from rc. That also gets rid of the ugly path crond used to have in ps(1) outputs. Further I renamed it to cron, as Paul Vixie likes it and is done by NetBSD. NOTE VERY WELL THE FOLLOWING: 1) Systems crontab changed. Every users crontab resides in /var/cron EXCEPT root's. This is a special crontab as it resides in /etc. Further it is the ONLY crontab file in which you specify usernames. See /usr/src/etc/crontab. This is also done by BSDI's BSD/386 as far as I know (they provided the patches for it anyway) 2) So you must delete root's crontab and reinstall the copy in /etc from /usr/src/etc. 'Must' is to much: the old installed crontab will work but cron will also try to 'run' /etc/crontab. 3) Last but not least: cron's logging is now done via syslog. Note that logging by cron is done lowercase when it logs about itsself and uppercase when it logs user events, like installing a new crontab. The default logfile file is the same as before: syslog.conf:cron.* /var/cron/log -Guido 1994-01-22 21:44:14 +01:00			`#minute hour mday month wday who command`
Cleaned up crontab from NetBSD, adjusted for FreeBSD. 1993-07-19 21:08:04 +02:00			`#`
Add a system to save entropy from /dev/random periodically so that it can be used to reseed at boot time. This will greatly increase the chances that there will be sufficient entropy available at boot time to prevent long delays. For /etc/rc, remove the vmstat and iostat runs from the attempt to provide some cheesy randomness if the files fail, since those programs are dynamically linked, and ldd seems to want some randomness to do its magic. Guidance and parameters for this project were provided by Mark Murray, based on the requirements of the Yarrow algorithm. Some helpful suggestions for implementation (including the tip about iostat and vmstat) were provided by Sheldon Hearn. All blame for problems or mistakes is mine of course. 2001-01-11 14:01:20 +01:00			`# save some entropy so that /dev/random can reseed on boot`
			`/3 * * * operator /usr/libexec/save-entropy`
			`#`
This was a mixed bag of spaces and ^I's. 1999-12-15 18:58:29 +01:00			`/5 * * * root /usr/libexec/atrun`
Cleaned up crontab from NetBSD, adjusted for FreeBSD. 1993-07-19 21:08:04 +02:00			`#`
			`# rotate log files every hour, if necessary`
Make the cutover to periodic and cron.d as discussed to death on committers for the past week. 1997-08-13 08:12:05 +02:00			`0 * * * * root newsyslog`
Cleaned up crontab from NetBSD, adjusted for FreeBSD. 1993-07-19 21:08:04 +02:00			`#`
Revert back to rev 1.24 as we have not come to a consensus if is is OK for a hung `daily' run to keep a `weekly' run from happening. Same for `monthly'. We have always run `weekly' and `monthly' reguardless of the execution status of `daily'. Until there is some consensus we should not change the behavior. 2000-12-11 19:38:49 +01:00			`# do daily/weekly/monthly maintenance`
			`1 3 * * * root periodic daily`
			`15 4 * * 6 root periodic weekly`
			`30 5 1 * * root periodic monthly`
Call adjkerntz -a every half hour from 0 to 4 am 1994-11-02 10:50:11 +01:00			`#`
			`# time zone change adjustment for wall cmos clock,`
			`# does nothing, if you have UTC cmos clock.`
			`# See adjkerntz(8) for details.`
This was a mixed bag of spaces and ^I's. 1999-12-15 18:58:29 +01:00			`1,31 0-5 * * * root adjkerntz -a`