Mike,
Maybe you missed my original report of this diald-0.99.1 problem, as I only
mentioned it parenthetically in a reply to another post. But I'm surprised no-one
else has mentioned it.
If I interrupt diald while it is actually in the process of establishing a
connection, eg. while the modem is still whistling, either by cycling the modem's
power or by sending "block" or "down", diald goes permanently insane. It appears to
go into a loop where it repeatedly spawns the connect script and immediately kills
it. It then won't respond to any more commands and you have to kill it.
I'm running on SuSE 6.1 with glibc 2.0.7 and a 2.2.10 kernel but the same problem
exists on 2.2.9 at least.
Can anyone else reproduce this problem?
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
