From owner-freebsd-current Mon Aug 10 10:40:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08081 for freebsd-current-outgoing; Mon, 10 Aug 1998 10:40:30 -0700 (PDT) (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 KAA08074 for ; Mon, 10 Aug 1998 10:40:26 -0700 (PDT) (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 UAA16852 for ; Mon, 10 Aug 1998 20:24:37 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id UAA14758 for current@freebsd.org; Mon, 10 Aug 1998 20:21:10 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id UAA06899; Mon, 10 Aug 1998 20:15:52 +0300 (EEST) (envelope-from archer) Date: Mon, 10 Aug 1998 20:15:52 +0300 (EEST) From: Alexander Litvin Message-Id: <199808101715.UAA06899@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Reminder : can't fork X-Newsgroups: grape.freebsd.current In-Reply-To: <199808091933.MAA07114@rah.star-gate.com> <199808092020.NAA07708@antipodes.cdrom.com> <19980810084921.21729@follo.net> Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980810084921.21729@follo.net> you wrote: EE> On Sun, Aug 09, 1998 at 01:20:11PM -0700, Mike Smith wrote: >> > >> > Occassionally, my system refuses to fork and pending on what I was doing >> > daemons such as sendmail die -- usually this is after I tried to compile >> > a big program such as mozilla however I have seen the bug surfaced when >> > I think I have not exhausted my swap space unfortunately most of the times >> > this happens I am at work and it is really hard to diagnose the problem. >> > >> > This problem has been around for about 6 months now. >> >> Pilot error. Your resource limits are too low. EE> Actually, it sound suspiciously like the old 'split page' bug where there EE> would be problems with forking after you had had a swap space exhaustion. EE> This was really easy to repoduce - after you ran out of swap, all daemons EE> would die when they tried to fork. You had to restart them to get them to EE> work again. I'm as sure as hell this bug is still in CURRENT. Everybody can see it himself. It ease easy to exhaust one's swap. If after that at list in 50% of cases forked sendmails don't die with SIGSEGV I'll eat my heat. EE> If this still can happen in some cases, it is _extremely_ important that we EE> get it fixed - IMO, we can't send out 3.0 with this kind of bug in it :-( EE> Eivind. --- Happiness, n.: An agreeable sensation arising from contemplating the misery of another. -- Ambrose Bierce, "The Devil's Dictionary" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message