From ccb0c9c2779946d1fee545d1786760cf7a1b7c76 Mon Sep 17 00:00:00 2001 From: Robin Greig Date: Sat, 16 Apr 2016 12:37:10 -0600 Subject: [PATCH] updated Pi204 crontab --- Pi204/Robin.crontab.20160416 | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Pi204/Robin.crontab.20160416 diff --git a/Pi204/Robin.crontab.20160416 b/Pi204/Robin.crontab.20160416 new file mode 100644 index 00000000..b5ed3462 --- /dev/null +++ b/Pi204/Robin.crontab.20160416 @@ -0,0 +1,29 @@ +# 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 + +#0 */4 * * * /home/robin/webtemp_1_sensor.py > /dev/null 2>&1 +0 */1 * * * /home/robin/webtemp_1_sensor.py > /dev/null 2>&1 +0 */1 * * * /home/robin/ReverseTunnel.sh > /dev/null 2>&1 +#5 */4 * * * /home/robin/MapleHouseTemp.sh > /dev/null 2>&1 +5 */1 * * * /home/robin/MapleHouseTemp.sh > /dev/null 2>&1 +