Re: Schedule Win32 Perl Scripts with AT

<rant>
at is @#^$%& broken. To compare it to cron(8) is an insult. It unschedules tasks at the faintest whiff of trouble. (Don't dare let your tasks fail, or they go into the great unscheduled limbo.) This is especially problematic if you're trying to deal with a network share that's periodically unavailable.

If you start trying to use at, do yourself a favor and make a batch file to reschedule your jobs, since you'll find yourself rescheduling them again and again and again and ...
</rant>

Comment on Re: Schedule Win32 Perl Scripts with AT

Replies are listed 'Best First'.
Re: Re: Schedule Win32 Perl Scripts with AT by BrowserUk (Patriarch) on Dec 04, 2002 at 22:36 UTC
An oft-used technique to work around some of those problems is to schedule a wrapper batch that invokes the real task. The wrapper task always succeeds, regardless of whether the real task does or not, thereby bypassing some of the problems. I used to have a fairly elaborate .cmd file that would also reschedule itself (with the name of the passed real command to be run) every hour 5 minutes etc if your needs are for a smaller granularity than daily. I might be able to dig a copy out if anyone was interested. Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color. Pick up your cloud down the end and "Yes" if you get allocated a grey one they *are* a bit damp under foot, but someone has to get them. Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory. Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.	[reply]
Re: Re: Schedule Win32 Perl Scripts with AT by Anonymous Monk on Dec 04, 2002 at 22:27 UTC
If you do it "again and again", then shouldn't you just schedule that rescheduling with at?	[reply]