Re: Script wrapper script

See perlfunc#do-EXPR; that sounds like what you want.

If these are scripts you don't have control over, though, I'd still fork, just to separate them and make sure they can't clobber anything in your script.

Comment on Re: Script wrapper script

Replies are listed 'Best First'.
Re^2: Script wrapper script by Anonymous Monk on Aug 17, 2005 at 19:00 UTC
I'll have to try using do, and see if I can retain the exit status of my intended script. I'm trying to avoid forking because there will be a LOT of scripts that're going to be launched from cron, and I'd rather not have two processes per script. As I'm sure the SAs would agree. In any event, I really don't want to try to replace cron with a custom scheduler system, but we definitely want to track what ran, how it completed, and log it somewhere. This seems like the best approach. Any other ideas? Thanks	[reply]

Replies are listed 'Best First'.

Re^2: Script wrapper script
by Anonymous Monk on Aug 17, 2005 at 19:00 UTC

I'm trying to avoid forking because there will be a LOT of scripts that're going to be launched from cron, and I'd rather not have two processes per script. As I'm sure the SAs would agree.

In any event, I really don't want to try to replace cron with a custom scheduler system, but we definitely want to track what ran, how it completed, and log it somewhere. This seems like the best approach. Any other ideas?

Thanks

[reply]