1 Significant changes for nfs-utils 1.1.0 - March/April 2007
3 - rpc.lockd is gone. One 3 old kernel releases need it.
4 - /sbin/{u,}mount.nfs{,4} is now installed so 'mount' will
5 use these to mount nfs filesystems instead of internal code.
6 + mount.nfs will check for 'statd' to be running when mounting
7 a filesystem which requires it. If it is not running it will
8 run "/usr/sbin/start-statd" to try to start it.
9 If statd is not running and cannot be started, mount.nfs will
10 refuse to mount the filesystem and will suggest the 'nolock'
12 - Substantial changes to statd
13 + The 'notify' process that must happen at boot has been split
14 into a separate program "sm-notify". It ensures that it
15 only runs once even if you restart statd. This is correct
17 + statd stores state in the files in /var/lib/nfs/sm/ so that
18 if you kill and restart it, it will restore that state and
19 continue working correctly.
20 + statd makes more use of DNS lookup and should handle
21 multi-homed peers better.
22 - If you export a directory as 'crossmnt', all filesystems
23 mounted beneath are automatically exported with the same
24 options (unless explicitly exported with different options).
25 - subtree_check is no-longer the default. The default is now
27 - By default the system 'rpcgen' is used while building
28 nfs-utils rather than the internal one.
31 Further notes on statd:
33 statd should be installed in /usr/sbin, not /sbin.
34 If you need to mount /usr via nfs, use 'nolock'
36 At boot time, run "/usr/sbin/sm-notify".
37 Run "statd" only when starting the NFS server.
38 "statd" should be run before starting the NFS server.
39 You do not need to start statd at boot time incase an
40 NFS filesystem is mounted. mount.nfs will take care of that.
42 Make sure /usr/sbin/start-statd will run statd with required