From owner-freebsd-current Fri Nov 6 13:42:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06775 for freebsd-current-outgoing; Fri, 6 Nov 1998 13:42:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06755 for ; Fri, 6 Nov 1998 13:41:52 -0800 (PST) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id XAA14346 for ; Fri, 6 Nov 1998 23:41:22 +0200 (EET) (envelope-from archer@grape.carrier.kiev.ua) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id XAA22795 for current@freebsd.org; Fri, 6 Nov 1998 23:40:55 +0200 (EET) (envelope-from archer@grape.carrier.kiev.ua) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.9.1/8.9.1) id XAA06359; Fri, 6 Nov 1998 23:33:37 +0200 (EET) (envelope-from archer) Date: Fri, 6 Nov 1998 23:33:37 +0200 (EET) From: Alexander Litvin Message-Id: <199811062133.XAA06359@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug X-Newsgroups: grape.freebsd.current In-Reply-To: <19981106183112.27770@follo.net> <19981106200028.23174@follo.net> Organization: Lucky Grape User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981106200028.23174@follo.net> you wrote: EE> On Fri, Nov 06, 1998 at 01:33:41PM -0500, David E. Cross wrote: >> >> Does this happen to everyone, I personally have *never* seen it happen, >> and I have run quite a few systems run with full memory utilization. EE> No. Unfortunately, we've not found any (or I at least don't know of EE> any) common factors between all the machines that have this problem. EE> David committed some patches a while back that he said _might_ help it EE> - I've not yet upgraded to test this. Unfortunately, DG's patches didn't solve the problem. May be, there are more than one bug "contributing". BTW, it seems that either 'make -j# buildworld' fires out more parallel jobs than it used to, or the total system memory footprint has increased. I mean, some three months ago my system easily survived -j32, without daemons dying, even without 'Suggest more swap space' -- it is for me a first sign that soon I'll have them dying. But now it needs only -j14 to be out of swap on the same system. EE> Eivind. --- Your lucky number has been disconnected. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message