Table of Contents
Reference chapter.
A crontab can also be tested. To do this you have to SSH to the machine, usually as admin to run the command.
For example, to test the my-brilliant-site.com crontab navigate to
/srv/my-brilliant-site.com/config/
and run symbiosis-crontab
--test crontab.
The my-brilliant-site.com crontab reads
# Send any output to Bob # MAILTO=bob@my-brilliant-site.com # # run at 18:40 every day # 40 18 * * * echo Hello Dave. # # run at 9am every Monday - Friday # 0 9 * * mon-fri wget http://www.my-brilliant-site.com/cron.php # # Run once a month # @monthly /usr/local/bin/monthly-job.sh
Therefore the output generated is
Environment ------------------------------------------------------------------------ HOME = /srv LOGNAME = admin PATH = /usr/local/bin:/usr/bin:/bin MAILTO = bob@my-brilliant-site.com ======================================================================== Jobs next due -- Local time 2010-06-17T17:57:37+01:00 ------------------------------------------------------------------------ Date Command ------------------------------------------------------------------------ 2010-06-17T18:40:00+01:00 echo Hello Dave. 2010-06-18T09:00:00+01:00 wget http://www.my-brilliant-site.com/cron.php 2010-07-01T00:00:00+01:00 /usr/local/bin/monthly-job.sh ========================================================================
The only environment variables that can be set within your crontab are PATH and MAILTO. All the rest are set automatically, and cannot be altered.