5.3 auto starting NFS by error

[bob at a1poweruser.com]

I think your missing the whole point. It's not suppose to be doing
this.  This is a release build error. In the 4.x releases the kernel
had NFS support complied into the default kernel, but when you have
no NFS statements in rc.conf those tasks in question are not auto
spawned.  Why would this behavior be changed in 5.3 to one that
consumes resources. It has to be a mistake.

If what you assert is true then when doing a source update to 5.3
why does these nfs tasks not auto spawn there.

You assertion that its designed to work that way it just plain silly
and only means you know not what you talk about.

Time to submit another bug report so maybe its gets fixed in 5.4


-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Kris
Kennaway
Sent: Saturday, April 02, 2005 9:03 PM
To: bob at a1poweruser.com
Cc: freebsd-questions at FreeBSD. ORG; Kris Kennaway
Subject: Re: 5.3 auto starting NFS by error

On Sat, Apr 02, 2005 at 08:43:47PM -0500, bob at a1poweruser.com wrote:
> This is a standard vanilla install from mini.iso cd with all the
> sysinstall questions answered as no.
> I have not made any changes to any /etc files.
> What was delivered in the install is what the current content is.
> The /etc/fstab as delivered does not have any nfs mounts.
> This is not a configuration error on my part. This is how the 5.3
> system gets installed for cd.
> This is a problem with how the sysinstall process configures the
> system.

The GENERIC (i.e. default) kernel is configured to allow NFS client
support, which means that the nfsiod kernel processes are spawned at
boot time.  If you don't want this, reconfigure your kernel to
disable
the NFS client support.  Or don't, because the resource usage is
negligible.

Kris

P.S. You're still top-posting.  If you can't be bothered to format
your posts properly, I won't bother to help you.