From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 20:55:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73EFC16A4CE for ; Thu, 7 Apr 2005 20:55:41 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id F28BB43D5F for ; Thu, 7 Apr 2005 20:55:40 +0000 (GMT) (envelope-from bob@a1poweruser.com) Received: from barbish ([69.172.31.81]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050407205536.DAEY2192.mta9.adelphia.net@barbish>; Thu, 7 Apr 2005 16:55:36 -0400 From: To: "Brooks Davis" Date: Thu, 7 Apr 2005 16:55:34 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <20050407202947.GB21190@odin.ac.hmc.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal cc: stable@freebsd.org Subject: RE: nfsiod tasks started in error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bob@a1poweruser.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 20:55:41 -0000 On Thu, Apr 07, 2005 at 04:11:55PM -0400, bob@a1poweruser.com 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. -- Brooks vfs.nfs.iodmin=0 in sysctl.conf did not stop those tasks from starting. I know that kill pid works but where can I bury a script containing the kill commands that will get run after those nfs tasks get started?