Bug #79760 for Sys-Manage: Scheduling not as advertised, Limitations depends on cron.

Firstly, the examples given didn't work/run at all. -runmod was undefined causing regexes to toss out. Please always check any variable is set prior to regexes, other comparisons, use. You should update the Limitations section to include this dependency until it can be removed, I've wasted plenty of my time on a product that doesn't deliver. There IS NO CRON, don't ask. There are plenty of reasons all staked up ranging from security to added load for LDAP queries to the Admins just don't want us to use it or even have it. I'm looking for a good replacement to shell code involving "sleep 86400". Know any? eagnmnmbd069:~$ cat atSched.pl use Sys::Manage::Schedule; my $s =Sys::Manage::Schedule->new(-runmod=>'-set'); $s->at('-',['10:26']); $s->run('echo "Hello World!!"'); eagnmnmbd069:~$ perl atSched.pl [30866]: Scheduling: -set You (####) are not allowed to use this program (crontab) See crontab(1) for more information [30866]: run: crontab ./atSched/atSched-crontab.txt You (####) are not allowed to use this program (crontab) See crontab(1) for more information [30866]: run: echo "Hello World!!" Hello World!! [30866]: run: crontab ./atSched/atSched-crontab.txt You (####) are not allowed to use this program (crontab) See crontab(1) for more information