Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 04 Feb 1995 16:40:09 +0000
From:      Ed Hudson <elh@p5.spnet.com>
To:        freebsd-hackers@FreeBSD.org
Cc:        elh@spnet.com
Subject:   kernel limits
Message-ID:  <199502041640.QAA06673@p5.spnet.com>

next in thread | raw e-mail | index | archive | help

	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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502041640.QAA06673>