Ch0k3r wrote:
>
> Thanx for all the help, I think i got it.
> I don't want a cron job to force the connection up since the connection
> doesn't have to stay up,
> it just has to be available. The business in question gets charges 4 cents
> a minute for phone calls.
> so staying up all the time can get expensive.
> On the topic of Rodneys post, if i read it correctly. if you have anything
> in the 'up' section the connection will stay up during the times specified?
> He said:
> >If you want it only to dial when it sees traffic
> >then delete everything above the word up including
> >the word up and it will respect the protocol rules
> >during the times it is not forced down.
>
Your statement is true, if you have up rules it will be forced up. If you
have only down rules then it will be forced down at those times, and dial
when it sees traffic during the non-forced down times.
> At 14:17 3/23/99 -0500, Kirk Lawson wrote:
> >
> >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.
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
--
-------------------------------------------------------------------------------
Rodney D. Holm [EMAIL PROTECTED]
Apexx Technology, Inc. http://www.apexxtech.com
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
