From owner-freebsd-current  Sun Mar 30 15:37:42 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA21182
          for current-outgoing; Sun, 30 Mar 1997 15:37:42 -0800 (PST)
Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA21169;
          Sun, 30 Mar 1997 15:37:08 -0800 (PST)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id RAA19210; Sun, 30 Mar 1997 17:34:39 -0600 (CST)
Message-Id: <199703302334.RAA19210@iworks.InterWorks.org>
Date: Sun, 30 Mar 1997 17:34:39 -0600 (CST)
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: freebsd-current@freebsd.org, gclarkii@main.gbdata.com, sos@freebsd.org
Subject: Re: pppd ?? do we have a maintainer ??
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> > > I have a couble of fixes to pppd (kernel level ppp) that makes
> > > it a little more usable (it doesn't work in 2.2.1 and current :( )
>
> > Huh?  You mean pppd?  The light/2 stuff must have broken it then, because
> > I'm running the snap from right before then and have never had a problem.
>
> That cant be :) unless you use it as a client only :)

I'm using it as a client only, and about once every month or
two it locks the system up tight forcing a cold reboot.  Usually
(actually every time I can remember it occurring), I am also
doing something as root.  When mounting a file system, or even
su'ing to root.

It's been doing this for probably close to a year now.  I can't
reliably reproduce it.  I've been tracking -current FWIW.

Dan Eischen
deischen@iworks.InterWorks.org