From owner-freebsd-hackers Tue Jan 21 16:26:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA25893 for hackers-outgoing; Tue, 21 Jan 1997 16:26:36 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA25874 for ; Tue, 21 Jan 1997 16:26:29 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vmqWF-0000dU-00; Tue, 21 Jan 1997 17:26:23 -0700 To: hackers@freebsd.org Subject: Cannot fork Date: Tue, 21 Jan 1997 17:26:23 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How to I get rid of the cannot fork messages? I have maxusers set to be 30 for my 486 box, yet I still get these messages from time to time. I just upgraded from Nov 24 -current to Jan 19-current and have found that the number of times I'm hitting this seems to be much greater. I had a build of ispell going, an emacs window and a find | xargs egrep from another xterm. Plus twm and xclock. This shouldn't run me out of process slots (ps auxww | wc said 50, a surprising round number). Any ideas on how I might track down this problem? I'm rebuilding my kernel now with MAX_CHILDREN set to be 256 rather than whatever the default is. We'll see if that is the problem. Over time I keep bumping limits and I'm fine for a while, but after a while I start to hit the cannot fork messages again. Thanks for any help you might be able to render in my endevors... Warner