From f51b5a5b0d20460ce9a530cf94431142aaa5f139 Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Mon, 19 Aug 2013 13:54:08 -0400 Subject: [PATCH] puppet: Move zephyr_mirror crontab into /etc/cron.d. (imported from commit e93e630704ce7e85346f54f095c642010058fc09) --- bots/zephyr-mirror-crontab | 26 -------------------------- 1 file changed, 26 deletions(-) delete mode 100644 bots/zephyr-mirror-crontab diff --git a/bots/zephyr-mirror-crontab b/bots/zephyr-mirror-crontab deleted file mode 100644 index a7f6001..0000000 --- a/bots/zephyr-mirror-crontab +++ /dev/null @@ -1,26 +0,0 @@ -SHELL=/bin/bash -# Edit this file to introduce tasks to be run by cron. -# -# Each task to run has to be defined through a single line -# indicating with different fields when the task will be run -# and what command to run for the task -# -# To define the time you can provide concrete values for -# minute (m), hour (h), day of month (dom), month (mon), -# and day of week (dow) or use '*' in these fields (for 'any'). -# -# Notice that tasks will be started based on the cron's system -# daemon's notion of time and timezones. -# -# Output of the crontab jobs (including errors) is sent through -# email to the user the crontab file belongs to (unless redirected). -# -# For example, you can run a backup of all your user accounts -# at 5 a.m every week with: -# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ -# -# For more information see the manual pages of crontab(5) and cron(8) -# -# m h dom mon dow command -35 * * * * env KRB5CCNAME=/tmp/krb5cc_1000.tmp kinit -k -t /home/humbug/tabbott.extra.keytab tabbott/extra@ATHENA.MIT.EDU; mv /tmp/krb5cc_1000.tmp /tmp/krb5cc_1000 -*/2 * * * * /home/humbug/api/bots/check-mirroring &> /var/run/nagios/check-mirroring-results-tmp; mv /var/run/nagios/check-mirroring-results-tmp /var/run/nagios/check-mirroring-results