This is what I changed my crontab entry to and I'm still getting items marked as long overdue and the patron is charged the cost of the item when they are only one day past due. 10 21 * * * /usr/share/koha/bin/cronjobs/longoverdue.pl --lost 100=1 --charge 1 --confirm Joe Atzberger wrote:
Tim --
In my opinion, the longoverdue.pl cronjobs fails to support multiple --lost arguments reliably, despite its example's claim to the contrary.
You can try executing the job with -v (verbose) and see if you don't have an unexpected range for your second case reported, like: starting range: X - Y with lost value 1
I recommend only using one --lost argument for now.
--Joe
On Wed, Feb 18, 2009 at 11:32 AM, Tim McMahon <tmcmahon@wlpl.org <mailto:tmcmahon@wlpl.org>> 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 <mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- 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