Paul Mackerras wrote:
>
> Brian Fisher <[EMAIL PROTECTED]> wrote:
>
> > Thanks for the info, it was a big help. I'm using kppp (K Desktop) to dial in
> > with, and it looks like it has some code that polls the ppp0 device to
> > determine when and if the connection is active. That bit of code seems to have
> > the side effect of causing read requests to be issued to the ppp0 device
> > while pppd is attempting to negotiate a connection, thus my
> > difficulties in getting connected. kppp isn't doing a read directly, but maybe
> > when the socket is opened UDP is attempting a read...
>
> I don't think it's kppp that is causing the problems. The socket
> calls that it is doing in the code you included won't generate reads
> on the serial port. More likely you have a getty or something trying
> to use the serial port.
I am not Brian but I am happy to report that the bug has been identified
(and fixed) due to the debugging work of Ian Gordon
<[EMAIL PROTECTED]>.
kppp has its own little scripting engine that uses a socket notifier to
poll the serial port. There was a race condition that could lead to a
situation where the notifier got accidentally re-enabled AFTER the end
of the script. Further data got read and .... taken away from pppd :(.
I hope that this case is closed now since it caused a flood of bug
reports I wasn't able to reproduce on my machine.
Harri.
.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
