Tim --<br><br>In my opinion, the longoverdue.pl cronjobs fails to support multiple --lost arguments reliably, despite its example's claim to the contrary. <br><br>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:<br>
<div style="margin-left: 40px;">starting range: X - Y with lost value 1<br></div><br>I recommend only using one --lost argument for now. <br><br>--Joe<br><br><br><div class="gmail_quote">On Wed, Feb 18, 2009 at 11:32 AM, Tim McMahon <span dir="ltr"><<a href="mailto:tmcmahon@wlpl.org">tmcmahon@wlpl.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Running Koha 3, we're having all items marked long overdue one day after<br>
the due date and patrons are charged the items replacement price. Our<br>
LOST status is 1=lost and 2=long overdue. The crontab entry is from<br>
crontab.example<br>
<br>
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost<br>
100=1 --charge 1 --confirm<br>
<br>
What else should I be checking to get long overdues to wait till books<br>
ar long ovedue?<br>
<font color="#888888"><br>
--<br>
Tim McMahon<br>
Technical Services<br>
West Liberty Public Library<br>
_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</font></blockquote></div><br>