From c2a3df31239249b2fb65e2552376daac0e49ae61 Mon Sep 17 00:00:00 2001
From: Christopher Browne <cbbrowne@ca.afilias.info>
Date: Wed, 27 Apr 2016 12:52:47 -0400
Subject: [PATCH] Saving crontab for user  on host

---
 cbbrowne.cbbrowne | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 cbbrowne.cbbrowne

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