Date: Sat, 26 Aug 1995 14:16:30 +0100 From: Colman Reilly <careilly@monoid.cs.tcd.ie> To: FreeBSD-gnats-submit@freebsd.org Subject: conf/708: CHILD_MAX set rather low by default? Message-ID: <199508261316.OAA04984@monoid.cs.tcd.ie> Resent-Message-ID: <199508261320.GAA17926@freefall.FreeBSD.org>
next in thread | raw e-mail | index | archive | help
>Number: 708 >Category: conf >Synopsis: CHILD_MAX set rather low by default? >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Aug 26 06:20:00 PDT 1995 >Last-Modified: >Originator: Colman Reilly >Organization: >Release: FreeBSD 2.0-BUILT-19950603 i386 >Environment: 2.0.5 Release kernel. >Description: It seems to me that the CHILD_MAX in the default configurations is a bit small, even for a single user machine: someone running X can easily wander over 40 processes. >How-To-Repeat: Compile from a GENERIC kernel. >Fix: I'd suggest putting # Under some circumstances it is necessary to make the default max # number of processes per user and open files per user more than the # defaults on bootup. (an example is a large news server in which # the uid, news, can sometimes need > 100 simultaneous processes running, # or perhaps a user using lot's of windows under X). options "CHILD_MAX=64" options "OPEN_MAX=128" into the GENERIC configuration, so that new users working from that as a reference will find it when they're rebuilding their kernel, rather than actually having to think about it. :-) Colman >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508261316.OAA04984>