Local change, not apropos to have in this repo
parent
2fe06e4ef5
commit
de2f95bc6f
@ -1,25 +0,0 @@
|
|||||||
* * * * * /home/cbbrowne/bin/cookie > /dev/null 2> /dev/null
|
|
||||||
2 2-5 * * * /home/cbbrowne/GitConfig/Scripts/cfcleanup > /dev/null 2> /dev/null
|
|
||||||
#2,22,42 * * * * /usr/bin/offlineimap -u Noninteractive.Quiet > /dev/null 2> /dev/null
|
|
||||||
# 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
|
|
Loading…
Reference in New Issue