fixing NFS related sysctl naming
Rick Macklem
rmacklem at uoguelph.ca
Thu May 5 14:10:45 UTC 2011
Hi,
Right now there are separate name paths for sysctls used by the
two NFS clients, which is awkward since scripts like to play
with them (currently using "vfs.nfs" which is the old one).
One thought I had was moving the SYSCTL()s and the global
variables they manipulate into the "nfslock" modules, which
is shared by both clients, so that changing "vfs.nfs.xxx"
will affect both NFS clients concurrently.
How does this idea sound?
Any other suggestions on how to best deal with this?
Thanks in advance for any comment, rick
More information about the freebsd-fs
mailing list