Maxime Henrion wrote: > With kenv(1) you can modify kernel environment variables, which hold the > tunables. Previously, you could only set those at boot time.
Note that there are some values which are used to determine the size of KVA space allocations, and changing them after boot, even if it's permitted, will have no real effect. For example, you can change the value of "maxfiles" with a sysctl, but doing so will not increase the number of simultaneous network connections your system will support, since the reserved space for tcpcb's and sockets is not increased. The kernel environment is most useful for diagnostic porposes, and for use in the way descrived in this thread -- to provide a means of passing parameters that should not be parameters to modules that should not need parameters in the first place. Many times, hacking the values post-boot will have little or no effect. It's too bad the things that will have no effect were exported as writeable, instead of resulting in an error. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
