On my system, sysctl(8) shows that vfs.nfs.iodmin is 4. And this is out of the box on a fresh install of 6.1 in which I told sysinstall that I wanted no NFS. Sounds like a bug. Now that you've explained where the knobs are, I see that I can work around it via lines in /boot/loader.conf, which can set sysctl variables at the time when the kernel is loaded. But the bug should be addressed in 6.2. If you're not running NFS, you don't need NFS- related processes laying around.
--Brett Glass At 02:42 PM 10/31/2006, Dan Nelson wrote: >In the last episode (Oct 31), Brett Glass said: >> I have no interest in running NFS (AKA "no file security") on my >> FreeBSD boxes, but have noticed that FreeBSD 6.x seems to start a >> daemon called "nfsiod" by default even when it is not configured as >> an NFS server or client. What's the best way to instruct the system >> not to start these processes, which take up resources and may be a >> security risk? Why isn't this done at sysinstall time? > >nfsiods are kernel threads that allow for parallel client requests from >a machine. You must still have some sort of NFS client functionality >in the kernel for them to exist, but you can tell them to quit by >setting the vfs.nfs.iodmax sysctl to 0. They should exit imediately. >In fact, since iodmin defaults to zero, there shouldn't be any running >unless you are actively using nfs. > >-- > Dan Nelson > [EMAIL PROTECTED] _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
