From owner-freebsd-current Mon Aug 10 00:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23453 for freebsd-current-outgoing; Mon, 10 Aug 1998 00:29:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23448 for ; Mon, 10 Aug 1998 00:29:49 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA03741; Mon, 10 Aug 1998 00:29:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199808100729.AAA03741@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Mon, 10 Aug 1998 08:49:21 +0200." <19980810084921.21729@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Aug 1998 00:29:16 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Your bug description sounds very similar to what I am experiencing however I can't reproduce the problem so far. Wrote a short program which allocates memory then touches every page -- repeated the same procedure till I ran out of swap space and the system kills my process which is okay. Daemons seems to stay up so I am going to have to wait till I can reproduce the problem . Regards, Amancio > 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. > > Actually, it sound suspiciously like the old 'split page' bug where there > would be problems with forking after you had had a swap space exhaustion. > This was really easy to repoduce - after you ran out of swap, all daemons > would die when they tried to fork. You had to restart them to get them to > work again. > > If this still can happen in some cases, it is _extremely_ important that we > get it fixed - IMO, we can't send out 3.0 with this kind of bug in it :-( > > Eivind. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message