# 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
*/1 * * * * sleep 29;/work/tools/main/ping.sh > /dev/null 2>&1
#*/5 0-3,5-23 * * * sleep 29;/work/tools/main/srvping.sh > /dev/null 2>&1
#0-14/1 9-23 * * * /work/tools/main/KITWATCH/starter.sh > /dev/null 2>&1
#15-55/10 9-23 * * * /work/tools/main/KITWATCH/starter.sh > /dev/null 2>&1
0 1 * * * sqlite3 /work/tools/main/KITWATCH/data/filedb.sqlite3 reindex > /dev/null 2>&1
0 * * * * . /work/tools/main/config.txt;crontab -l > /home/hallcom/cron_${NODE}.txt;chown hallcom.hallcom /home/hallcom/cron_${NODE}.txt > /dev/null 2>&1
49 8 * * * /work/tools/main/cronupd.sh | tee /work/backup/log/cronupd-`date +\%Y\%m\%d_\%H\%M\%S`.txt > /dev/null 2>&1
5 7 * * * /work/tools/main/log.sh > /dev/null 2>&1