Skip Menu |

This queue is for tickets about the Schedule-Cron-Events CPAN distribution.

Report information
The Basics
Id: 59325
Status: resolved
Priority: 0/
Queue: Schedule-Cron-Events

People
Owner: KOHTS [...] cpan.org
Requestors: floyd [...] atc.no
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.8
Fixed in: (no value)



Subject: Months range error-checking chokes on january (0)
The months range must contain at least one valid value at C:/strawberry/perl/site/lib/Schedule/Cron/Events.pm line 187 Schedule::Cron::Events::cronLineToRanges('33 13 1 0 * /dev/null') called at C:/strawberry/perl/site/lib/Schedule/Cron/Events.pm line 32 Schedule::Cron::Events::new('Schedule::Cron::Events', '33 13 1 0 * /bin/sh', 'Seconds', 1279042469) called at FilerobotTask.pm line 217 FilerobotTask::schedule_next('FilerobotTask=HASH(0xdacc34)') called at FilerobotTask.pm line 100 FilerobotTask::next('FilerobotTask=HASH(0xdacc34)') called at C:\Documents and Settings\Floyd\Mine dokumenter\FilerobotService.pl line 13 I believe the cron entry '33 13 1 0 *' is correct and means "every january 1st at 13:33", Schedule::Cron::Events seems to choke on the month. If I try '33 13 1 1 *' instead, it is (correctly) interpreted as "every february 1st at 13:33"
Show quoted text
> > I believe the cron entry '33 13 1 0 *' is correct > and means "every january 1st at 13:33", Schedule::Cron::Events > seems to choke on the month. > > If I try '33 13 1 1 *' instead, it is (correctly) interpreted as "every > february 1st at 13:33"
Here's an excerpt from (5) crontab: field allowed values ----- -------------- minute 0-59 hour 0-23 day of month 1-31 month 1-12 (or names, see below) day of week 0-7 (0 or 7 is Sun, or use names) So I guess you've misinterpreted documentation. Resolving for now, but feel free to ask further questions. Sorry reply took so long, just noticed the ticket.