From owner-freebsd-hackers Sat Feb 4 16:40:39 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id QAA13756 for hackers-outgoing; Sat, 4 Feb 1995 16:40:39 -0800 Received: from p5.spnet.com (elh.com [204.156.130.1]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id QAA13750 for ; Sat, 4 Feb 1995 16:40:37 -0800 Received: from localhost (localhost [127.0.0.1]) by p5.spnet.com (8.6.9/8.6.6) with SMTP id QAA06673; Sat, 4 Feb 1995 16:40:09 GMT Message-Id: <199502041640.QAA06673@p5.spnet.com> X-Authentication-Warning: p5.spnet.com: Host localhost didn't use HELO protocol To: freebsd-hackers@FreeBSD.org cc: elh@spnet.com Subject: kernel limits Date: Sat, 04 Feb 1995 16:40:09 +0000 From: Ed Hudson Sender: hackers-owner@FreeBSD.org Precedence: bulk i'd like to request that you folks consider 2 changes to kernel limits to be incorporated in the general release. in order for me to do the sort of work that i do (chip design, cad development), the first thing that i do with each new release of FBSD is change these limits. i know of other organizations using FBSD (or NBSD) in real engineering applications, and they have similar problems with the current limtis. General Kernel Limits: 1) bump /usr/src/sys/sys/param.h:MAXSYMLNK from 8 to something reasonable, such as 32. why: i've worked in many environments where paths traverse 8 or more symlnks. if you further try to simulate that environment from somewhere else (eg, home), that can add a few more symbolic links, etc. 2) bump up CHILD_MAX from 40 to something reasonable, say 128. why: i've compiled large software systems that spawn a deep series of subshells and (then do final makes) and these can frequently run into MAXUPRC, which is set to CHILD_MAX. also, simulating make-called-tools from other environments sometimes adds a few shell script levels... also, limit problems like this, encountered deep within scripts, can be hard for the unwary to see and debug. further, multi-desktop window managers, such as fvwm, encourage large process counts, by reducing the management complexity of many windows. so how 'bout it? -elh elh@spnet.com