From owner-freebsd-stable@FreeBSD.ORG Thu Apr 7 21:06:09 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 4EFA516A4CE for ; Thu, 7 Apr 2005 21:06:09 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC27243D53 for ; Thu, 7 Apr 2005 21:06:08 +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 <20050407210608.DQYF2192.mta9.adelphia.net@barbish>; Thu, 7 Apr 2005 17:06:08 -0400 From: To: "Dan Nelson" Date: Thu, 7 Apr 2005 17:06:07 -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: <20050407204747.GP64927@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 21:06:09 -0000 In the last episode (Apr 07), bob@a1poweruser.com said: > 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? The answer is to remove "options NFS" from your kernel and recompile. If you enable the nfs client, you automatically get "nfsiod" threads created for you, just like if you have acpi compiled into your kernel, you get "acpi_task*" threads, or if you have a keyboard plugged in, you get an "irq1: atkbd0" thread. Neither of those existed in 4.* and you're not complaining about them. What is it about those four nfsiod threads that upsets you so much? -- Dan Nelson dnelson@allantgroup.com Plan and simple. It's a security hole. If no nfs is selected in sysinstall then there should not be any nfs stuff started at all.