From owner-freebsd-current Tue Oct 13 03:49:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07325 for freebsd-current-outgoing; Tue, 13 Oct 1998 03:49:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07318; Tue, 13 Oct 1998 03:49:05 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id MAA29466; Tue, 13 Oct 1998 12:48:48 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA17917; Tue, 13 Oct 1998 12:48:45 +0200 (MET DST) Message-ID: <19981013124845.25955@follo.net> Date: Tue, 13 Oct 1998 12:48:45 +0200 From: Eivind Eklund To: alk@pobox.com 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> <13859.2587.145715.385630@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <13859.2587.145715.385630@avalon.east>; from Tony Kimball on Tue, Oct 13, 1998 at 03:15:06AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 13, 1998 at 03:15:06AM -0500, Tony Kimball wrote: > 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. Check out what is eating your memory. Likely a restart of X will free up enough memory that it won't re-occur for a long time - netscape tend to make X leak (in what may be an interaction with the VM system, possibly through vfork()). > : 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. I've not seen any commits that should fix it, and I've been on the lookout for them. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message