From 40c29c7ca8eef1459979a451d421692e92878ec6 Mon Sep 17 00:00:00 2001 From: Tomas Cohen Arazi Date: Tue, 13 Sep 2016 14:42:32 -0300 Subject: [PATCH] Bug 2389: (followup) Add documentation and fix use case Signed-off-by: Tomas Cohen Arazi --- misc/cronjobs/overdue_notices.pl | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/misc/cronjobs/overdue_notices.pl b/misc/cronjobs/overdue_notices.pl index 0b9d623..cdff966 100755 --- a/misc/cronjobs/overdue_notices.pl +++ b/misc/cronjobs/overdue_notices.pl @@ -69,6 +69,7 @@ overdue_notices.pl -borcat category code that must be included -borcatout category code that must be excluded -t only include triggered overdues + --test Run in test mode. No changes will be made on the DB. -list-all list all overdues -date emulate overdues run for this date -email type of email that will be used. Can be 'email', 'emailpro' or 'B_email'. Repeatable. @@ -159,6 +160,13 @@ the cron schedule to ensure proper behavior. Add the --triggered option for daily cron, at the risk of no notice being generated if the cron fails to run on time. +=item B<-test> + +This option makes the script run in test mode. + +In test mode, the script won't make any changes on the DB. This is usefull +for debugging configurations. + =item B<-list-all> Default items.content lists only those items that fall in the @@ -813,7 +821,7 @@ END_SQL attachments => [$attachment], to_address => $admin_email_address, } - ); + ) unless $test_mode; } } -- 2.7.4