Bug #17883 for Schedule-Cron: Cron-scheduled Routine works 64-65 times an then stops (under Windows 2000)

Mon Feb 27 13:46:09 2006 Guest - Ticket created

Subject:

Cron-scheduled Routine works 64-65 times an then stops (under Windows 2000)

I'm using this Module during a Perl-Script for Monitoring an Windows- Service every 5 Minutes. The Script is implemented as a Services on an W2K-Server. It works fine, the Routine runs exactly as defined in the "cron-entry", but after 64-65 times it stops ´calling the Monitoring-Routine. Cron-Entry: 0,5,10,15,20,25,30,35,40,45,50,55 * * * * When i use a shorter time-intervall, f.e. 1 Minutes, it also runs 64- 65 times. Perl 5.8.7 Schedule-Cron 0.9

Sun Nov 05 12:17:46 2006 roland [...] cpan.org - Taken

Sun Nov 05 12:44:04 2006 roland [...] cpan.org - Correspondence added

On Mo. 27. Feb. 2006, 13:46:09, guest wrote: Show quoted text

> I'm using this Module during a Perl-Script for Monitoring an Windows- > Service every 5 Minutes. The Script is implemented as a Services on an > W2K-Server. It works fine, the Routine runs exactly as defined in > the "cron-entry", but after 64-65 times it stops ´calling the > Monitoring-Routine. > > Cron-Entry: 0,5,10,15,20,25,30,35,40,45,50,55 * * * * > > When i use a shorter time-intervall, f.e. 1 Minutes, it also runs 64- > 65 times. > > Perl 5.8.7 > Schedule-Cron 0.9 >

Can you verify this also with the newest Version 0.96 ? What happens, if you use the 'nofork=>1' option when creating Cron::Schedule ? As you might know from the README, there is unfortunately not much support for Windows but I heard that it works with the newest ActiveState Perl. With 'nofork' there shouldn't be any problem anyway .... ciao, ...roland

Sun Nov 05 12:44:06 2006 The RT System itself - Status changed from 'new' to 'open'

Sun Nov 05 12:44:07 2006 roland [...] cpan.org - Status changed from 'open' to 'stalled'

Fri Mar 20 12:32:54 2009 roland [...] cpan.org - Status changed from 'stalled' to 'rejected'