I discovered this under 3.4-R, and checked that it's still the case
for 4.0-RC.
I'm putting together a box that has no reason whatsoever to use or
provide any NFS services at all.
It was thus with a sense of "POLA violation" that I happened across the
message
Mounting NFS file systems
in the boot-up messages.
Turns out that the stanza that generates that (in /etc/rc) looks like:
echo -n "Mounting NFS file systems"
mount -a -t nfs
echo .
...as in, this isn't conditional on anything.
OK; fine. Maybe I'm not a programmer (any more), but this seems to
work OK:
-----%<----------------
--- rc Tue Feb 8 22:32:40 2000
+++ /tmp/rc Mon Feb 14 14:11:01 2000
@@ -191,9 +191,14 @@
network_pass1
fi
-# Mount NFS filesystems.
-echo -n "Mounting NFS file systems"
-mount -a -t nfs
+case ${nfs_client_enable} in
+[Yy][Ee][Ss])
+ # Mount NFS filesystems.
+ echo -n "Mounting NFS file systems"
+ mount -a -t nfs
+ ;;
+esac
+
echo .
# Whack the pty perms back into shape.
----->%----------------
Downside is that it's possible that there are machines that actually *do*
act as NFS clients, even though nfs_client_enable is not set affirmatively.
Then again, it could be argued that a new release would be one of the
better times to make this kind of change, eh...? :-)
(I'd do a send-pr, but I don't actually have a 4.0-RC system running at
the moment, and I need to get this system running ASAP; the above was
based on a 4.0-RC filesystem that is accessible from another machine, and
I actually did the equivalent patch to the 3.4-R system, which survived the
experiment... though, as noted, it doesn't use NFS.)
Cheers,
david
--
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
