I have a script that needs to be running continuously as a service on a cluster, so it can failover to another node if need be. The cluster software is working fine, but the cron part is a little iffy.

Specifically, when I launch it using perl script.pl, the script

• waits until its scheduled time (in the case below, every 1 minute), according to the entry that's been added using the add_entry method,
• then keeps calling that same subroutine over and over.

Anybody ran into this before? I'm open to using something other than Schedule::Cron, assuming it will work on a clustered failover system, so normal unix cron won't work. This is my code: ...

use Schedule::Cron;

#Variable declarations
my $rootdir = "/testdir";

# Initialize and run the cron job.  Note that this is continuous by na
+ture.
my $cron = new Schedule::Cron(\&dispatcher,
                             );
#$cron->add_entry("0 15 * * * *",
$cron->add_entry("0-59 * * * * *",
                 {'subroutine' => \&GetStats,
                  }
                );

$cron->run(detach=>1, pid_file=>"$rootdir/$0.pid");


################################################
# Subroutines to be called
sub dispatcher {
   print "ID:   ",shift,"\n";
   print "Args: ","@_","\n";
}
[download]