<snip>
--but that seems just as strange as, say, putting a 'sleep' clause in
one of your scripts. i'm sure there is a way to call a system
command in perl and say:
</snip>
There is one large (and often useful) difference between using sleep and
cron. When you use cron you can have more than one instance running at
the same time (if the task takes more than X minutes to complete). This
is usually considered a bug. Remember cron starts a task every X
minutes and sleep stops the current process for X seconds.
<snip>
> system ('sleep 300');
>
> --or something like that.
>
> --anyone care to offer a better idea? i'm sure they're out there ...
>
</snip>
<snip href=perldoc -f sleep>
Causes the script to sleep for EXPR seconds, or
forever if no EXPR. May be interrupted if the
process receives a signal such as `SIGALRM'.
Returns the number of seconds actually slept. You
probably cannot mix `alarm' and `sleep' calls,
because `sleep' is often implemented using
`alarm'.
</snip>
--
Today is Prickle-Prickle the 24th day of Chaos in the YOLD 3168
Or is it?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
