Date: Wed, 14 Dec 2005 01:20:47 -0500 From: Chuck Swiger <cswiger@mac.com> To: Michael Dexter <dexter@ambidexter.com> Cc: freebsd-questions@freebsd.org Subject: Re: kern.maxdsiz "big memory/tuning" questions Message-ID: <439FB9BF.6090305@mac.com> In-Reply-To: <a06230935bfc4e3834caa@[192.168.1.30]> References: <a06230935bfc4e3834caa@[192.168.1.30]>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Dexter wrote: [ ... ] > However, I am not clear if: > > 1. It is permitted to use "M" and "G" notation (kern.maxsiz="1G")? - > some say yes, some say no and I would prefer not risk the system not > booting. Using "1G" or some number followed by "M" is working for me in 5.x and 6.0. > 2. Which tunables actually matter beyond kern.maxdsiz? Some say only > kern.maxdsiz and some suggest all three. 'man tuning' and the handbook > (~/handbook/configtuning-kernel-limits.html) only goes into maxfiles and > maxusers. Searches of this list and Google have yeilded what you see above. > > Could someone please share some wisdom or docs on this matter? The stuff listed in /etc/defaults/loader.conf is probably the most complete reference outside of the kernel source code itself, but you might find looking at the corresponding "sysctl -d" output for the variables in question. Note that the loader and sysctl don't always use the same name. Other than that, check what limits you're seeing in the shell you run. And double-check under /bin/sh too, for cron jobs or stuff started at boot. :-) -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?439FB9BF.6090305>