On Mon, Oct 22, 2007 at 07:06:17PM -0700, David Fox wrote:
> On 10/22/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> >
> > if you set a cron job to run every 10 seconds then it will run at
> > 12:00.00, 12:00.10, 12:00.20 etc regardless of how long the execution
>
> Of course, just like th
On 10/22/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
>
> if you set a cron job to run every 10 seconds then it will run at
> 12:00.00, 12:00.10, 12:00.20 etc regardless of how long the execution
Of course, just like the phone company, cron has minute resolution.
--
To UNSUBSCRIBE, emai
On Sun, Oct 21, 2007 at 05:56:44PM -0600, Telly Williams wrote:
> Hi,
>
> Hopefully this doesn't sound crazy, but what would be the
> pros/cons of using a script with a sleeper instead of a script
> via cron? Seems the same to me(?). Thanks.
it entirely depends on what you are
Kevin writes:
> Well, 'sleep' is for a one time delay of a command like 'at' whereas
> 'cron' is for doing things regularly. But I'm suprised that you didn't
> get that from reading the 'man' pages. You did, didn't you?
Before cron at was used for periodic events by having it reschedule
itself. W
On Sun, Oct 21, 2007 at 05:56:44PM -0600, Telly Williams wrote:
> Hi,
>
> Hopefully this doesn't sound crazy, but what would be the
> pros/cons of using a script with a sleeper instead of a script
> via cron? Seems the same to me(?). Thanks.
Well, 'sleep' is for a one time dela
Hi,
Hopefully this doesn't sound crazy, but what would be the
pros/cons of using a script with a sleeper instead of a script
via cron? Seems the same to me(?). Thanks.
--
Telly Williams
"Knowledge Is Power"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
6 matches
Mail list logo