>David Douthitt wrote:
>>
>> I have noticed a number of odd-ball reactions to different combinations of
>> diald FIFO commands. Consider the following (assume no connection):
>>
>> 1. Enter UP, then UP again. Seems like diald then sets about trying to
>> bring up TWO identical connections.
>>
>> 2. Enter UP, then BLOCK. The block command is effectively ignored.
BLOCK
>> should cancel all up commands and reset the modem to its "blocked" state.
>>
>> 3. Enter FORCE. Nothing happens. An isolated FORCE command should bring
>> up the link.
>>
>> 4. Enter UP, pause until dialing is under way (or thereabouts), then
enter
>> DOWN. Nothing happens.
>>
>> 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.
>>
>> What are people's thoughts?
>
>Use dctrl from the diald rpm on contrib.redhat.com
>It does these things, and correctly.
I don't normally use X on my system; this rules out dctrl.
In any case, dctrl should ONLY be a front-end to the diald FIFO. The
fact that IT does thing correctly does not change the fact that the FIFO
does not.
David Douthitt
[EMAIL PROTECTED] -or- [EMAIL PROTECTED]
"It's not over till the fat guy in the plaid shirt gets
thrown out by the ushers." - Harold, "The Red Green Show"
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
