On Thu, Apr 07, 2005 at 01:29:48PM -0700, Brooks Davis wrote: > On Thu, Apr 07, 2005 at 04:11:55PM -0400, [EMAIL PROTECTED] wrote: > > During sysinstall answered no to the server and client nfs questions > > and after installed completed and system rebooted I see task > > nfsiod1,2,3,4 running in output of ps ax command. This was not the > > case in any of the 4.x releases. This can be looked upon as a > > security leak. This may be a error in the new boot up process. This > > was first reported 1/16/2004 in 5.2 RC2 as Problem Report kern/61438 > > and again in 5.3 as Problem Report kern/79539 > > > > I tried to run /usr/local/etc/rc.d/killnfs.sh script to kill these > > unwanted tasks but that does not work. > > > > Any suggestions on how I can kill these bogus nfs tasks as part of > > boot up or what to change in the boot up process so these tasks > > don't get started in the first place? Doing a manual recompile of > > the kernel to remove the nfs statements is not a viable solution. > > nfsiod now runs as a kernel process and is control by these sysctls: > > vfs.nfs.iodmaxidle: 120 > vfs.nfs.iodmin: 4 > vfs.nfs.iodmax: 20 > > It looks like setting vfs.nfs.iodmin=0 and then klling them off works. > We probably should think about changing the default to 0 and setting > appropriate values via /etc/rc.d/nfs. Over all, I can't say this is a > very high priority though patches would certaintly be accepted.
This was a deliberate change by Peter, since if you have NFSCLIENT in the kernel it's assumed you want to use the machine as a NFS client. Kris
pgphN5d3NY5sz.pgp
Description: PGP signature
