yup -- The KOHA_CRON_PATH is a place holder -- so you know where to put in the actual path to the cronjob script for example on one of my servers it looks like this 20 0 * * * perl /home/koha/kohaclone/misc/cronjobs/longoverdue.pl -- lost 5=2 --lost 10=1 --charge 1 --confirm Cheers, Brendan --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com --------------------------------------------------------------------------------------------------------------------------------- On Feb 18, 2009, at 9:29 AM, Tim McMahon wrote:
Thanks for the speedy reply. I already have that line in the crontab. Are you saying I can't use the $KOHA_CRON_PATH and need to replace that with the actual path? I have $KOHA_CRON_PATH defined at the beginning of the crontab.
Brendan Gallagher wrote:
Hi Tim -- You are at the right place for what you want... That script needs to be placed in your crontab and you need to replace the first part of it with your path to koha_cronjobs. So that script will have items age to longoverdue after 20 days and then become lost after 100 days and charge the patron replacement fees. -Brendan --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com --------------------------------------------------------------------------------------------------------------------------------- On Feb 18, 2009, at 8:32 AM, Tim McMahon wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com
-- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org