>
> Sep 9 21:32:52 localhost pppd[471]: Using interface ppp0
> Sep 9 21:32:52 localhost pppd[471]: Connect: ppp0 <--> /dev/modem
> Sep 9 21:32:58 localhost pppd[471]: Remote message: Login Succeeded
> Sep 9 21:32:58 localhost pppd[471]: local IP address 207.142.161.143
> Sep 9 21:32:58 localhost pppd[471]: remote IP address 207.142.161.5
> Sep 9 21:33:21 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
> at 115200
> Sep 9 21:33:21 localhost pppd[521]: pppd 2.3.5 started by root, uid 0
> Sep 9 21:33:21 localhost pppd[521]: Device modem is locked by pid 471
> Sep 9 21:33:21 localhost pppd[521]: Exit.
> Sep 9 21:33:51 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
> at 115200
> Sep 9 21:33:52 localhost pppd[538]: pppd 2.3.5 started by root, uid 0
> Sep 9 21:33:52 localhost pppd[538]: Device modem is locked by pid 471
> Sep 9 21:33:52 localhost pppd[538]: Exit.
> Sep 9 21:34:22 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
> at 115200
> Sep 9 21:34:22 localhost pppd[545]: pppd 2.3.5 started by root, uid 0
> Sep 9 21:34:22 localhost pppd[545]: Device modem is locked by pid 471
> Sep 9 21:34:22 localhost pppd[545]: Exit.
>
hrm. This could be caused by many things. again there is still too little
information. Try adding the "debug" param to your pppd and read the man page
about how to squeze out any more information. As far as I can see from this
it could just be that redhat's ppp scripts are being a little too zelous
(they were at least when I ran redhat).
-- Bruce A. Locke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html