From owner-freebsd-current Tue Dec 1 14:26:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25872 for freebsd-current-outgoing; Tue, 1 Dec 1998 14:26:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25861 for ; Tue, 1 Dec 1998 14:26:28 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA12666 for freebsd-current@FreeBSD.ORG; Tue, 1 Dec 1998 23:26:08 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id CD33E1536; Tue, 1 Dec 1998 22:52:14 +0100 (CET) Date: Tue, 1 Dec 1998 22:52:14 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: 'junk pointer' with inetd ... Message-ID: <19981201225214.A12792@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: ; from garman@earthling.net on Tue, Dec 01, 1998 at 09:30:44AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4856 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to garman@earthling.net: > and to those who believe that this bug is only caused when one is "near > swap capacity" -- the swapinfo above would refute that :) Another datapoint: I've seen the message "add more swap: 386 MB" on a machine with 192 MB RAM + 192 MB swap, swap being used at less than one MB (!). I was forced to restart inetd. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message