I've been on vacation, didn't see this until now.
I agree with most of these; however, there's a special case not
mentioned: what happens when a force is issued while blocked, or a block
is issued while forced? I would add that force should cancel any block,
block should cancel any force.
I believe these follow the principle of least suprise. Some people may
think that they'd like their link to finish dialing even though they've
blocked the connection, but when the dial attempt is caused by an up,
and the phone line is busy (it happens - I've cron jobs), I can't run
block; diald continues to try and bring up the connection forever, even
though it's blocked. Since it wasn't a packet that started it, it
doesn't time out. I basically have to kill diald.
Ed
David Douthitt wrote:
>
> I would recommend the following reactions to different commands:
>
> 1. BLOCK: if the link is up (or in process of coming up) everything is
> cancelled and the link is returned to a DOWN (and BLOCKed) state.
>
> 2. FORCE: if the link is down, the link is brought up and locked.
>
> 3. UP: if the link is up or in process of coming up, ignore the command.
>
> 4. DOWN: if the link is in process of coming up, cancel all appropriate
> processes and return the link to a down state.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
