On Tue, 23 Mar 1999, Giulio Orsero wrote:
>> What i need to have is: durning business hours the link
>> should come up for any request and stay up for at least 10
>> minutes after.
> Handle this with filter rules (maybe in the include).
Offhand, one rule (for each protocol type?) should be adequate
to cover that policy (but you'll find your link going up too
often ... I would just stick with the standard.filter and modify
some of the timeouts for my needs.)
>> then during non hours it shouldn't come up at all.
> handle this with a restrict.
Closer, but not quite:
> restrict 17:31:00 23:59:59 6-7 * *
> or-restrict 00:00:00 08:00:00 6-7 * *
> down
> restrict * * * * *
> include phone.filter
Try this:
restrict * 7:59:59 1-5 * *
or-restrict 17:30:00 * 1-5 * *
or-restrict * * 0 * *
or-restrict * * 6 * *
down
restrict * * * * *
include phone.filter
There are a couple of problems with this strategy, though:
1) It doesn't handle holidays. There is a nice program called
remind which can handle extremely complex date/time
specifications. If you really want to handle every possible
case, you could use remind to send commands to the diald control
fifo.
2) Someday, you're going to have to work early or late or on a
weekend, probably on some emergency project, and it would be a
real bummer to have the network just cut out on you totally. It
would be even worse for a colleague who had no idea what was
happening. Downing the link totally in non-work hours seems a
little extreme to me. Perhaps it could be done in stages. Or
perhaps you could write a little program to override the up/down
commands that could be run manually by someone working late.
Ed
--
Ed Doolittle <mailto:[EMAIL PROTECTED]>
"Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
