From owner-freebsd-current  Tue Sep 30 15:14:10 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA25587
          for current-outgoing; Tue, 30 Sep 1997 15:14:10 -0700 (PDT)
Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA25520;
          Tue, 30 Sep 1997 15:13:33 -0700 (PDT)
Received: (from root@localhost)
	by bmccane.uit.net (8.8.7/8.8.5) id RAA20779;
	Tue, 30 Sep 1997 17:11:06 -0500 (CDT)
Date: Tue, 30 Sep 1997 17:11:06 -0500 (CDT)
From: Wm Brian McCane <root@bmccane.uit.net>
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG
Subject: RE: PPP problems
In-Reply-To: <XFMail.970930131737.Shimon@i-Connect.Net>
Message-ID: <Pine.BSF.3.91.970930170745.20741A-100000@bmccane.uit.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 30 Sep 1997, Simon Shapiro wrote:

> 
> Hi Wm Brian McCane;  On 30-Sep-97 you wrote: 
>  
> ...
> 
> >  and another kernel build and rebooted.  Once again everything worked,
> >  until I 
> >  went to eat dinner....
> 
> You see!  Had you stayed at the keyboard... :-)
I tried to use this argument with my wife too.  I have the still healing 
bite marks to prove it 8(.
 
> >       Okay, here's what I am seeing:
> >  
> >       I use kernel PPP for a full time connection to the InterNet
> >       My connection gets dropped every 5 hours by my ISP
> >               (shouldn't unlimited mean UNLIMITED!)
> 
> Yup!  Here too...
> 
> To this i might add:
I haven't seen these errors, what level of debugging do you have to have 
turned on for them?

> Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [15 3 29],
> 3
> Sep 29 10:52:30 sendero /kernel.sendero: ppp0: no compressor for [18 4 8], 4
> Sep 30 01:21:27 sendero /kernel.sendero: ppp0: no compressor for [15 3 29],
...

> and ...
> 
> Sep 30 12:24:09 sendero /kernel.sendero: ppp0: line error 4000000
> Sep 30 12:24:09 sendero last message repeated 2 times
> Sep 30 12:24:10 sendero /kernel.sendero: sio2: 3 more silo overflows (total
> 3)
> Sep 30 12:38:23 sendero /kernel.sendero: ppp0: line error 4000000
> Sep 30 12:38:24 sendero /kernel.sendero: sio2: 1 more silo overflow (total
> 4)
...

I have pppd run automatically from cron.  It checks to see if the port is 
already locked, and if not it starts processing.  So what I see in 
messages file is:
Sep 29 08:00:01 bmccane pppd[13936]: Device cuaa1 is locked by pid 75
Sep 29 08:00:01 bmccane last message repeated 13 times
Sep 29 08:00:01 bmccane pppd[12853]: Device cuaa1 is locked by pid 75
Sep 29 08:00:01 bmccane last message repeated 9 times
Sep 29 08:00:01 bmccane pppd[13936]: Device cuaa1 is locked by pid 75
Sep 29 08:00:01 bmccane last message repeated 25 times
Sep 29 08:00:03 bmccane pppd[12853]: Device cuaa1 is locked by pid 75

Nice to know that even without a valid `pid' file in /var/run, the port 
is still locked.  This also happens after I try to kill the #*$(&% program.

	brian