Date: Thu, 7 Apr 2005 17:06:07 -0400 From: <bob@a1poweruser.com> To: "Dan Nelson" <dnelson@allantgroup.com> Cc: stable@freebsd.org Subject: RE: nfsiod tasks started in error Message-ID: <MIEPLLIBMLEEABPDBIEGEELOHDAA.bob@a1poweruser.com> In-Reply-To: <20050407204747.GP64927@dan.emsphone.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
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MIEPLLIBMLEEABPDBIEGEELOHDAA.bob>