summaryrefslogtreecommitdiffstats
path: root/etc/crontab
diff options
context:
space:
mode:
authorobrien <obrien@FreeBSD.org>2000-12-11 18:38:49 +0000
committerobrien <obrien@FreeBSD.org>2000-12-11 18:38:49 +0000
commit89e57811313c801ee801f009580d9a4beeb7c656 (patch)
tree5cb0e9614d4b440d5bba3f3fdd8663a04b69dd45 /etc/crontab
parente1a91d9a98a905a06b9bf9b6b2ad326ad586eec7 (diff)
downloadFreeBSD-src-89e57811313c801ee801f009580d9a4beeb7c656.zip
FreeBSD-src-89e57811313c801ee801f009580d9a4beeb7c656.tar.gz
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.
Diffstat (limited to 'etc/crontab')
-rw-r--r--etc/crontab11
1 files changed, 4 insertions, 7 deletions
diff --git a/etc/crontab b/etc/crontab
index b64a804..784980c 100644
--- a/etc/crontab
+++ b/etc/crontab
@@ -13,13 +13,10 @@ HOME=/var/log
# rotate log files every hour, if necessary
0 * * * * root newsyslog
#
-# Do daily/weekly/monthly maintenance.
-# These four rules make sure the right maintenance scripts run one
-# after the other on the right day.
-1 3 2-31 * 0-5 root periodic daily
-1 3 2-31 * 6 root periodic daily weekly
-1 3 1 * 0-5 root periodic daily monthly
-1 3 1 * 6 root periodic daily weekly monthly
+# 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.
OpenPOWER on IntegriCloud