"Ivan Voras" <[EMAIL PROTECTED]> writes: > The macro is defined and used exactly once, in this file. Other files > probably use maxfiles.
maxfiles is the real value; it's a loader tunable, and more importantly, it can be modified at run time through the kern.maxfiles sysctl variable. MAXFILES is simply the default value to which maxfiles is initialized. > The problem is - since it's in an #ifdef block > - is it defined anywhere else? A quick grep yields only this: > > conf/NOTES:options MAXFILES=999 > conf/options:MAXFILES opt_param.h > > I don't know how config interacts with the source - does it shadow the > subr_param.c value? Yes. If you use the MAXFILES option in your kernel config, config(8) will add a corresponding #define MAXFILES to opt_param.h. I doubt anyone would complain (or even notice) if you removed it entirely. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
