1 This is version 1.0.1 of nfs-utils, the Linux NFS utility package.
6 Home page: http://sourceforge.net/projects/nfs/
8 To use the 'gss' support you must have kerberos-5 development
10 Otherwise use "--disable-gss"
12 To use nfsv4 support you need libevent and libnfsidmap development
13 libraries. They are available from
14 http://www.monkey.org/~provos/libevent/
15 http://www.citi.umich.edu/projects/nfsv4/linux/libnfsidmap/
16 Otherwise use --disable-nfsv4
21 Unpack the sources and run these commands:
26 To install binaries and documenation, run this command:
33 Getting nfs-utils for the first time:
35 git clone git://linux-nfs.org/nfs-utils
37 Updating to the latest head after you've already got it.
41 Building requires that autotools be installed. To invoke them
46 Finally, build as usual as above.
48 3. DAEMON STARTUP ORDER
50 This nfs-utils packages does not provide any scripts for starting
51 various daemons as mast distributions replace them with their own, so
52 any scripts we package would not get much testing.
53 Instead, we explain the dependencies involved in startup so that
54 scripts can be written to work correctly.
58 Name service (host name lookup) should be working before any
59 NFS services are started.
61 "portmap" must be running before any NFS services (server or
64 Normally network interfaces should be configured first as well,
65 though this isn't critical for the NFS server (providing name
66 service is handled locally).
71 A/ mount -t nfsd /proc/fs/nfsd
72 This filesystem needs to be mount before most daemons,
73 particularly exportfs, mountd, svcgssd, idmapd.
74 It could be mounted once, or the script that starts each daemon
75 could test if it is mounted and mount it if not.
78 These supply services to nfsd and so should be started before
79 rpc.nfsd. Where they come between mounting the nfsd filesystem
80 and starting the nfsd server is not important.
81 idmapd is only need for NFSv4 support.
83 C/ exportfs -av ; rpc.mountd
84 If it important that exportfs be run before mountd so that
85 mountd is working from current information (in
87 It is also important that both of these are run before
89 If not, any NFS requests that arrive before mountd is started
90 will get replied to with a 'Stale NFS File handle' error.
92 D/ rpc.statd --no-notify
93 It is best if statd is started before nfsd though this isn't
94 critical. Certainly it should be at most a few seconds after
96 When nfsd starts it will start lockd. If lockd then receives a
97 lock request it will communicate with statd. If statd is not
98 running lockd will retry, but it won't wait forever for a
100 Note that if statd is started before nfsd, the --no-notify
101 option must be used. If notify requests are sent out before
102 nfsd start, clients may try to reclaim locks and, on finding
103 that lockd isn't running, they will give up and never reclaim
105 rpc.statd is only needed for NFSv2 and NFSv3 support.
108 Starting nfsd will automatically start lockd. The nfs server
109 will now be fully active and respond to any requests from
113 This will notify any client which might have locks from before
114 a reboot to try to reclaim their locks. This should start
115 immediately after rpc.nfsd is started so that clients have a
116 chance to reclaim locks within the 90 second grace period.
117 sm-notify is only needed for NFSv2 and NFSv3 support.
123 This should be run shortly after boot and before any NFS
124 filesystems are mounted with remote-locking support -
125 filesystems can be mounted with "-o nolock" before sm-notify.
126 This is appropriate for '/', '/usr', and '/var'.
129 (I need some guidance here).
131 C/ statd should be run before any NFSv2 or NFSv3 filesystem is
132 mounted with remote locking (i.e. without -o nolock).
133 'mount' will try to use "/usr/sbin/start-statd" to start statd
134 if it is not already running, so there is no need to explicitly
135 start statd in boot-time scripts.
137 3.3. SERVER/CLIENT INTERACTIONS
140 Both the server and the client need sm-notify to be run.
141 It should be run after the NFS server is started, but before
142 and NFS filesystems are mounted with remote locking.
145 Both the server and the client need rpc.statd to be running.
146 Each should try to start when they need it.
149 (I need some guidance here).
156 -- the nfs-utils developers
157 <nfs@lists.sourceforge.net>