OK, so why does CVS want pppd to hang up? I'm presuming that the Hangup (SIGHUP) isn't a crash, right? Is this a CVS bug?
V. This is from the troubleshooting log from pppd shows: Mar 3 01:11:07 localhost pppd[3947]: secondary DNS address 207.69.188.185 Mar 3 01:11:07 localhost pppd[3947]: Script /etc/ppp/ip-up started (pid 3958) Mar 3 01:11:07 localhost pppd[3947]: Script /etc/ppp/ip-up finished (pid 3958), status = 0x0 Mar 3 01:18:44 localhost pppd[3947]: Hangup (SIGHUP) Mar 3 01:18:44 localhost pppd[3947]: Modem hangup Mar 3 01:18:44 localhost pppd[3947]: Script /etc/ppp/ip-down started (pid 4013) Mar 3 01:18:44 localhost pppd[3947]: Connection terminated. Mar 3 01:18:44 localhost pppd[3947]: Connect time 7.7 minutes. Mar 3 01:18:44 localhost pppd[3947]: Sent 39456 bytes, received 22065 bytes. Mar 3 01:18:44 localhost pppd[3947]: Waiting for 1 child processes... Mar 3 01:18:44 localhost pppd[3947]: script /etc/ppp/ip-down, pid 4013 Mar 3 01:18:44 localhost pppd[3947]: Script /etc/ppp/ip-down finished (pid 4013), status = 0x0 Mar 3 01:18:44 localhost pppd[3947]: Exit.
