1 ==================================
2 Administrative interfaces for nfsd
3 ==================================
4
5 Note that normally these interfaces are used o
6 nfs-utils.
7
8 nfsd is controlled mainly by pseudofiles under
9 which is normally mounted at /proc/fs/nfsd/.
10
11 The server is always started by the first writ
12 nfsd/threads.
13
14 Before doing that, NFSD can be told which sock
15 writing to nfsd/portlist; that write may be:
16
17 - an ascii-encoded file descriptor, w
18 bound (and listening, for tcp) sock
19 - "transportname port", where transpo
20 "udp", "tcp", or "rdma".
21
22 If nfsd is started without doing any of these,
23 udp and one tcp listener at port 2049 (see nfs
24
25 On startup, nfsd and lockd grace periods start
26 0 to nfsd/threads. All locks and state are th
27
28 Between startup and shutdown, the number of th
29 or down by additional writes to nfsd/threads o
30 nfsd/pool_threads.
31
32 For more detail about files under nfsd/ and wh
33 fs/nfsd/nfsctl.c; most of them have detailed c
34
35 Implementation notes
36 ====================
37
38 Note that the rpc server requires the caller t
39 removal of listening sockets, and startup and
40 For nfsd this is done using nfsd_mutex.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.