From owner-freebsd-bugs Fri Oct 20 07:43:30 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA06386 for bugs-outgoing; Fri, 20 Oct 1995 07:43:30 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA06381 for ; Fri, 20 Oct 1995 07:43:27 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA09119; Fri, 20 Oct 1995 10:43:14 -0400 Date: Fri, 20 Oct 1995 10:43:14 -0400 From: "Garrett A. Wollman" Message-Id: <9510201443.AA09119@halloran-eldar.lcs.mit.edu> To: Jerry.Kendall@vmicls.com (Jerry Kendall) Cc: freebsd-bugs@FreeBSD.ORG Subject: Running out of processes In-Reply-To: <9510201323.AA08228.gonzo@vmicls.com> References: <9510201323.AA08228.gonzo@vmicls.com> Sender: owner-bugs@FreeBSD.ORG Precedence: bulk < I have 'maxusers' set to 20; > therefore, according to the formula, I > should have (20 + (16 * maxusers)) = 340 > processes as my upper limit. > according to top is 60. I can close some of the > 'xterm' windows. The process numbers go down, I > add more and it goes up. But, it seems to stop > at 60. There is another limit, on the number of children a process is allowed to create, which is accessible from the `limit' or `ulimit' (depending on your shell) command. On my machine, bash's `ulimit -a' reports: max user processes 40 csh's `limit' reports: maxproc 40 You need to fiddle one of these numbers; see your shell's documentation for how. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant