setting MAILTO=youremailaddress might get you some error reports as well -reed 2010/5/20 Christopher Curry <ccurry@amphilsoc.org>:
Greg,
Thanks for the point in the right direction. I totally forgot about the ENV variables. That will probably take care of it and it explains why the script didn't run. I wish I could have seen the error message about not being about to find the perl modules. I would have recognized it.
Cheers,
Christopher Curry Assistant Technical Librarian / Assistant IT Officer
American Philosophical Society 105 South Fifth Street Philadelphia, PA 19106-3386 Tel. (215) 599-4299
ccurry@amphilsoc.org
Main Library number: (215)440-3400 APS website: http://www.amphilsoc.org
On 05/19/2010 12:15 PM, Greg Barniskis wrote:
On 5/19/2010 10:34 AM, Christopher Curry wrote: ...
Here is my crontab:
"0 3 * * 2-6 perl /usr/local/src/kohaclone/misc/cronjobs/cleanup_database.pl -v --sessions --zebraqueue 10 >>/var/log/koha/cleanup_database.log"
...
Any obvious issues with my configuration? Any ideas how I can make this work?
Your crontab example doesn't show you setting the environmental variables that may be needed (PERL5LIB and KOHA_CONF). See the examples from the web page below and modify the paths as needed for your system. You likely have these variables specified for your shell (so running the same command from the shell works), but cron needs these values too.
http://wiki.koha.org/doku.php?id=en:development:cronjobs
Also, this may not apply to your OS, but whenever I have cron issues on FreeBSD, ensuring that absolute paths are specified can help. So I'd personally use "/usr/bin/perl" as the command, not just "perl", or even skip that entirely and let the system figure it out from the specified script's #! line (again, YMMV with OS flavor).
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha