From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 20:34: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 85C8516A4E9 for ; Thu, 7 Apr 2005 20:34:41 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0809843D4C for ; Thu, 7 Apr 2005 20:34:41 +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 <20050407203440.BPON2192.mta9.adelphia.net@barbish>; Thu, 7 Apr 2005 16:34:40 -0400 From: To: "Dan Nelson" Date: Thu, 7 Apr 2005 16:34:39 -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: <20050407202213.GO64927@dan.emsphone.com> 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:34:41 -0000 In the last episode (Apr 07), bob@a1poweruser.com said: > 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 Both of those PRs should be closed as not-a-bug, I think. nfsiod threads simply allow multiple concurrent NFS requests. In 4.*, with no nfiod processes running, you can still use NFS (just more slowly than with them). In 5.*, they are auto-created as kernel threads during bootup. > I tried to run /usr/local/etc/rc.d/killnfs.sh script to kill these > unwanted tasks but that does not work. They aren't tasks, but kernel threads. Just like pagedaemon, swapper, g_event, irq*, swi*, and a couple dozen other threads created by the kernel. > 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. Why not? If you want to disable NFS, that's the only way. -- Dan Nelson dnelson@allantgroup.com You did not answer my question. how can I kill these bogus nfs tasks as part of the boot up or what to change in the boot up process so these tasks don't get started in the first place? What is a work around with out compiling the kernel?