Date: Thu, 7 Apr 2005 15:47:47 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: bob@a1poweruser.com Cc: stable@freebsd.org Subject: Re: nfsiod tasks started in error Message-ID: <20050407204747.GP64927@dan.emsphone.com> In-Reply-To: <MIEPLLIBMLEEABPDBIEGMELMHDAA.bob@a1poweruser.com> References: <20050407202213.GO64927@dan.emsphone.com> <MIEPLLIBMLEEABPDBIEGMELMHDAA.bob@a1poweruser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050407204747.GP64927>