Date: Tue, 16 May 2006 21:32:38 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Bill Moran <wmoran@collaborativefusion.com> Cc: questions@freebsd.org Subject: Re: Is MAXFILES still valid in a kernel config option? Message-ID: <20060516183238.GB9209@gothmog.pc> In-Reply-To: <20060516132827.0ed23256.wmoran@collaborativefusion.com> References: <20060516113537.3257b373.wmoran@collaborativefusion.com> <20060516160645.GA8079@gothmog.pc> <20060516132827.0ed23256.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-05-16 13:28, Bill Moran <wmoran@collaborativefusion.com> wrote: >On Tue, 16 May 2006 19:06:45 +0300 >Giorgos Keramidas <keramida@ceid.upatras.gr> wrote: >>On 2006-05-16 11:35, Bill Moran <wmoran@collaborativefusion.com> wrote: >>> >>> Using 6.1, is MAXFILES still honored in the kernel config? >>> >>> I know I can adjust this via sysctl, but setting it in the >>> kernel config is more conducive to our deployment >>> methodology. >> >> Yes. The option is still valid even in CURRENT. >> >> The `src/sys/kern/subr_param.c' file contains: >> >> 64 #ifndef MAXFILES >> 65 #define MAXFILES (maxproc * 2) >> 66 #endif >> >> and the option is still present in `src/sys/conf/NOTES'. > > Thanks. I thought it a little odd that NOTES groups it under > this category: > # Yet more undocumented options for linting. > > Seemed like something that was liable to silently break ... I'm not sure what the real plans are around there, but (AFAIK) at least for the RELENG_6 branch, now that the option is part of RELENG_6 it should remain there for the entire lifetime of the branch :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060516183238.GB9209>