I've had the 'persist' option fail for me similarly, but without the strange 'tcsetattr' bug. This is with PPPoE (for an ADSL connection), and has occurred in the past when the PPP connection has been terminated at the ISP end (during faults, or sometimes load balancing).
Jul 4 01:10:01 bluesky pppd[32014]: No response to 3 echo-requests Jul 4 01:10:01 bluesky pppd[32014]: Serial link appears to be disconnected. Jul 4 01:10:01 bluesky pppd[32014]: Connect time 4271.3 minutes. Jul 4 01:10:01 bluesky pppd[32014]: Sent 366052693 bytes, received 1306815812 bytes. Jul 4 01:10:01 bluesky pppd[32014]: Script /etc/ppp/ip-down started (pid 7523) Jul 4 01:10:01 bluesky pppd[32014]: sent [LCP TermReq id=0x2 "Peer not responding"] Jul 4 01:10:01 bluesky pppd[32014]: Script /etc/ppp/ip-down finished (pid 7523), status = 0x0 Jul 4 01:10:04 bluesky pppd[32014]: sent [LCP TermReq id=0x3 "Peer not responding"] Jul 4 01:10:07 bluesky pppd[32014]: Connection terminated. Jul 4 01:10:07 bluesky pppd[32014]: Modem hangup Jul 4 01:10:32 bluesky pppd[32014]: Terminating on signal 15 Jul 4 01:10:32 bluesky pppd[32014]: Exit. 'debug' is set to on, as is 'persist' and 'maxfail 0' After these log entries turn up, there is no pppd process to be found. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
