G'day, I have seen similar behaviour using the sarge pppd.
It happens on my system when pppd has option "persist" and it receives a LCP Term Req. The ppp connection terminates, the pid file is removed, but pppd is left running. It does not attempt to re-connect as you would think with the "persist" option. I suspect it continues to "hold" the serial port (unconfirmed, but I have to "poff" before "pon" will work correctly). I am uncertain if this condition can be achieved without the "persist" option, but it wouldn't surprise me. I think the correct behaviour would be to attempt to reconnect if "persist" is on. However, terminating pppd would be better than just hanging around doing nothing. I find pppd's management of pid files disturbing; there are many cases where pppd is running but the pid file is not present. The pid file is only present when the ppp link is up, not always when pppd is running. This seems counter to generally accepted use of pid files. -- Donovan Baarda <[EMAIL PROTECTED]> http://minkirri.apana.org.au/~abo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
