From owner-freebsd-current  Tue Oct 13 01:16:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA19400
          for freebsd-current-outgoing; Tue, 13 Oct 1998 01:16:16 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from poboxer.pobox.com (port17.prairietech.net [208.141.230.94])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19391;
          Tue, 13 Oct 1998 01:16:09 -0700 (PDT)
          (envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.7.3) id DAA08359; Tue, 13 Oct 1998 03:15:07 -0500 (CDT)
From: Tony Kimball <anthony.kimball@east.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 13 Oct 1998 03:15:06 -0500 (CDT)
X-Face: O9M"E%K;(f-Go/XDxL+pCxI5<W_e*r7B8ojMD.5+qDgOp4/\gTQEgbOoBqf:Vtl*aW:<;9/
	UIVk'U^XhYg+v#r~*X<$Q=_ik@5:%E}pl]9|9|:]WLW8n:fLgg0~cfwWRBQxK/HSG0b1D/gljJC$qp
	b=HDF@+"H<|fXy`w#$8#6A"!F:>*gr[=FN@Y`cl1.Tn
Reply-To: alk@pobox.com
To: eivind@yes.no
Cc: current@FreeBSD.ORG, dg@FreeBSD.ORG
Subject: Re: inetd is ill? syslogd is anemic?
References: <13854.19308.314677.685227@avalon.east>
	<199810092335.TAA25121@khavrinen.lcs.mit.edu>
	<13854.56585.707371.316487@avalon.east>
	<19981010200607.56951@follo.net>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <13859.2587.145715.385630@avalon.east>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Quoth Eivind Eklund on Sat, 10 October:
: This is a known, OLD bug.  It was one of the bugs introduced or
: exposed by John Dysons changes to the VM system.  He was working on
: this at the time he left, if I understood correctly.

Thanks.  I can confirm that you have correctly diagnosed the problem,
in as much as killing and restarting inetd stopped it from happenning
to inetd -- the disease moved on to syslogd.  Similarly, restarting
syslogd fixed that, and a few hours later it moved on to sendmail.
Restarting sendmail has kept it away for the past hour or two.

: My machine is a PPro-based box - I don't know if this matter.  I seem
: to remember it also happening after I upgraded to 80MB; I know it
: happened when I had 64MB, at least.

Mine is dual PPro 64MB as well, so this config is likely to make it
easier to reproduce.  Meanwhile, I think I'll upgrade my memory 
(as Garrett Wollman suggested) after all, and see if it goes away --
although like as not a kernel update and recompile will suffice.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message