From owner-freebsd-current Sun Aug 9 22:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11563 for freebsd-current-outgoing; Sun, 9 Aug 1998 22:24:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles217.castles.com [208.214.165.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11537 for ; Sun, 9 Aug 1998 22:23:58 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA09698; Sun, 9 Aug 1998 22:22:06 -0700 (PDT) Message-Id: <199808100522.WAA09698@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Reminder : can't fork In-reply-to: Your message of "Sun, 09 Aug 1998 14:39:50 PDT." <199808092139.OAA07390@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Aug 1998 22:22:06 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Pilot error is for sure a possibility however it does not explain why > sendmail dies when I am compiling mozilla from my account. I think that > this problem has been reported by other users. "Cannot fork" is either "too many processess (for you or the system in toto)" or some other resource starvation. If you're not out of memory or file descriptors, then you've hit the limit on the maximum number of processes. Let's guess that this is a FAQ; what is the value of 'maxusers' in your kernel config? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message