[Koha] Items marked long overdue one day after due date

[Brendan Gallagher]

Hey Tim --

As Joe suggest below - have you tried running the command with the  
minus v ( -v ) flag set.  This would need to be run from the command  
line and not through crontab (and you can run at anytime).  It should  
print most everything that the perl script is doing on your command  
window.

Give that a try and see if it helps you determine what's going on.

-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 at bywatersolutions.com
---------------------------------------------------------------------------------------------------------------------------------






On Feb 19, 2009, at 12:40 PM, Tim McMahon wrote:

> 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 at wlpl.org
>> <mailto:tmcmahon at 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 at lists.katipo.co.nz <mailto:Koha at lists.katipo.co.nz>
>>    http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Koha mailing list
>> Koha at 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 at wlpl.org	http://www.wlpl.org
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha