One reason you might want to use a cron job in favor of the 'restrict'
setting is to allow diald to continue running.
For instance, you want diald forced up during 7 - 6 but on demand dialing
all other times. You would then put in a cron command to 'dialdc force'
at 7:00 and another cron command to 'dialdc unforce' at 18:00.
peace favor your sword
----------
From: David Taylor
Sent: Tuesday, March 23, 1999 6:41 PM
To: LKLawson; Jean-Michel Lacroix
Cc: Ch0k3r; 'LINUX-DI@SMTP <[EMAIL PROTECTED]>'
Subject: Re: Control
On Tue, 23 Mar 1999, Jean-Michel Lacroix wrote:
>
> Could you set up a cron job that would start diald at the beginning of
> business hours and kill diald when the non-business hours starts?
Why bother? diald contains a way to do this sort of thing inbuilt, using
restrict.. However, i'm not sure whats wrong with his current setup
--
David Taylor
E-Mail: [EMAIL PROTECTED]
ICQ: 268004
[Remove .spam from e-mail to reply]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
