summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristopher Browne <cbbrowne@ca.afilias.info>2016-04-27 12:52:47 -0400
committerChristopher Browne <cbbrowne@ca.afilias.info>2016-04-27 12:52:47 -0400
commitc2a3df31239249b2fb65e2552376daac0e49ae61 (patch)
tree9845a00cb9778a5fbfdc1929f2326b894777b2c4
parentf59c4b03facd80cab913c6612a899392dd42ebb8 (diff)
Saving crontab for user on host
-rw-r--r--cbbrowne.cbbrowne25
1 files changed, 25 insertions, 0 deletions
diff --git a/cbbrowne.cbbrowne b/cbbrowne.cbbrowne
new file mode 100644
index 0000000000..622e4eedf8
--- /dev/null
+++ b/cbbrowne.cbbrowne
@@ -0,0 +1,25 @@
+* * * * * /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