Date: Mon, 10 Aug 1998 08:49:21 +0200 From: Eivind Eklund <eivind@yes.no> To: Mike Smith <mike@smith.net.au>, Amancio Hasty <hasty@rah.star-gate.com> Cc: current@FreeBSD.ORG Subject: Re: Reminder : can't fork Message-ID: <19980810084921.21729@follo.net> In-Reply-To: <199808092020.NAA07708@antipodes.cdrom.com>; from Mike Smith on Sun, Aug 09, 1998 at 01:20:11PM -0700 References: <199808091933.MAA07114@rah.star-gate.com> <199808092020.NAA07708@antipodes.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980810084921.21729>