From owner-freebsd-hackers  Sat Dec 21 21:01:20 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id VAA19102
          for hackers-outgoing; Sat, 21 Dec 1996 21:01:20 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA19097
          for <hackers@freebsd.org>; Sat, 21 Dec 1996 21:01:17 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA29311; Sat, 21 Dec 1996 22:01:01 -0700 (MST)
Date: Sat, 21 Dec 1996 22:01:01 -0700 (MST)
Message-Id: <199612220501.WAA29311@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: roberto@keltia.freenix.fr (Ollivier Robert)
Cc: hackers@freebsd.org
Subject: Re: innd can't remalloc
In-Reply-To: <Mutt.19961222012503.roberto@keltia.freenix.fr>
References: <199612201742.SAA04883@uriah.heep.sax.de>
	<Pine.BSF.3.95.961221222006.1390B-100000@server.zsb.th-darmstadt.de>
	<Mutt.19961222012503.roberto@keltia.freenix.fr>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> While I'm at this, is there a known problem with either pppd or the vn swap
> files in 2.1.5 ? We've stopped using both for a while and the machine
> hasn't crahsed yet...

I ran our dedicated PPP link over the internet using 2.1.5 for months
with an uptime of 160+ days using pppd.  We recently upgraded to Frame
Relay and 2.1.6.1, but I never had any problems with kernel pppd.


Nate