From: Ian Walls Date: Wed, 7 Dec 2011 00:12:04 +0000 (-0500) Subject: Bug 7326: longoverdue.pl hardcoded to 366 days maximum X-Git-Url: http://git.rot13.org/?a=commitdiff_plain;h=1f5f4981c098a7aa2a4323107dd98379a52a4c6e;p=koha.git Bug 7326: longoverdue.pl hardcoded to 366 days maximum Adds --maxdays command line flag to longoverdue.pl to allow the user to specify their own $endrange value. Because sometimes 366 isn't enough! Also adds help documentation for both --quiet and --maxdays params Signed-off-by: Chris Cormack Simple change, works well Signed-off-by: Paul Poulain --- diff --git a/misc/cronjobs/longoverdue.pl b/misc/cronjobs/longoverdue.pl index 38435446d3..e3648d526b 100755 --- a/misc/cronjobs/longoverdue.pl +++ b/misc/cronjobs/longoverdue.pl @@ -39,7 +39,7 @@ use Getopt::Long; my $lost; # key=lost value, value=num days. my ($charge, $verbose, $confirm, $quiet); -my $endrange = 366; # FIXME hardcoded - don't deal with anything overdue by more than this num days. +my $endrange = 366; GetOptions( 'lost=s%' => \$lost, @@ -47,6 +47,7 @@ GetOptions( 'confirm' => \$confirm, 'verbose' => \$verbose, 'quiet' => \$quiet, + 'maxdays=s' => \$endrange ); my $usage = << 'ENDUSAGE'; @@ -68,6 +69,11 @@ This script takes the following parameters : --confirm confirm. without this option, the script will report the number of affected items and return without modifying any records. + --quiet suppress summary output. + + --maxdays Specifies the end of the range of overdue days to deal with (defaults to 366). This + value is universal to all lost num days overdue passed. + examples : $PERL5LIB/misc/cronjobs/longoverdue.pl --lost 30=1 Would set LOST=1 after 30 days (up to one year), but not charge the account.