1NFS.CONF(5) File Formats Manual NFS.CONF(5)
2
6 nfs.conf - general configuration for NFS daemons and tools
7
9 /etc/nfs.conf
10
12 This file contains site-specific configuration for various NFS daemons
13 and other processes. Most configuration can also be passed to pro‐
14 cesses via command line arguments, but it can be more convenient to
15 have a central file. In particular, this encourages consistent config‐
16 uration across different processes.
17 When command line options are provided, they override values set in
19 this file. When this file does not specify a particular parameter, and
20 no command line option is provided, each tool provides its own default
21 values.
22 The file format supports multiple sections, each of which can contain
24 multiple value assignments. A section is introduced by a line contain‐
25 ing the section name enclosed in square brackets, so
26 [global]
27 would introduce a section called global. A value assignment is a sin‐
28 gle line that has the name of the value, an equals sign, and a setting
29 for the value, so
30 threads = 4
31 would set the value named threads in the current section to 4. Leading
32 and trailing spaces and tab are ignored, as are spaces and tabs sur‐
33 rounding the equals sign. Single and double quotes surrounding the
34 assigned value are also removed. If the resulting string is empty, the
35 whole assignment is ignored.
36 Any line starting with “#” or “;” is ignored, as is any blank line.
38 If the assigned value started with a “$” then the remainder is treated
40 as a name and looked for in the section [environment] or in the pro‐
41 cesses environment (see environ(7)). The value found is used for this
42 value.
43 The value name include is special. If a section contains
45 include = /some/file/name
46 then the named file will be read, and any value assignments found
47 there-in will be added to the current section. If the file contains
48 section headers, then new sections will be created just as if the
49 included file appeared in place of the include line. If the file name
50 starts with a hyphen then that is stripped off before the file is
51 opened, and if file doesn't exist no warning is given. Normally a non-
52 existent include file generates a warning.
53 Lookup of section and value names is case-insensitive.
55 Where a Boolean value is expected, any of true, t, yes, y, on, or 1 can
57 be used for "true", while false, f, no, n, off, or 0 can be used for
58 "false". Comparisons are case-insensitive.
59
62 The following sections are known to various programs, and can contain
63 the given named values. Most sections can also contain a debug value,
64 which can be one or more from the list general, call, auth, parse, all.
65 When a list is given, the members should be comma-separated.
66 general
68 Recognized values: pipefs-directory.
69 See blkmapd(8), rpc.idmapd(8), and rpc.gssd(8) for details.
71 exports
74 Recognized values: rootdir.
75 Setting rootdir to a valid path causes the nfs server to act as
77 if the supplied path is being prefixed to all the exported
78 entries. For instance, if rootdir=/my/root, and there is an
79 entry in /etc/exports for /filesystem, then the client will be
80 able to mount the path as /filesystem, but on the server, this
81 will resolve to the path /my/root/filesystem.
82 exportd
85 Recognized values: threads, state-directory-path
86 See exportd(8) for details.
88 nfsdcltrack
91 Recognized values: storagedir.
92 The nfsdcltrack program is run directly by the Linux kernel and
94 there is no opportunity to provide command line arguments, so
95 the configuration file is the only way to configure this pro‐
96 gram. See nfsdcltrack(8) for details.
97 nfsd Recognized values: threads, host, port, grace-time, lease-time,
100 udp, tcp, vers2, vers3, vers4, vers4.0, vers4.1, vers4.2, rdma,
101 Version and protocol values are Boolean values as described
103 above, and are also used by rpc.mountd. Threads and the two
104 times are integers. port and rdma are service names or numbers.
105 See rpc.nfsd(8) for details.
106 mountd Recognized values: manage-gids, descriptors, port, threads,
109 reverse-lookup, state-directory-path, ha-callout.
110 These, together with the protocol and version values in the
112 [nfsd] section, are used to configure mountd. See rpc.mountd(8)
113 for details.
114 The state-directory-path value in the [mountd] section is also
116 used by exportfs(8).
117 statd Recognized values: port, outgoing-port, name, state-directory-
120 path, ha-callout.
121 See rpc.statd(8) for details.
123 lockd Recognized values: port and udp-port.
126 See rpc.statd(8) for details.
128 sm-notify
131 Recognized values: retry-time, outgoing-port, and outgoing-addr.
132 See sm-notify(8) for details.
134 gssd Recognized values: verbosity, rpc-verbosity, use-memcache, use-
137 machine-creds, use-gss-proxy, avoid-dns, limit-to-legacy-enc‐
138 types, context-timeout, rpc-timeout, keytab-file, cred-cache-
139 directory, preferred-realm.
140 See rpc.gssd(8) for details.
142 svcgssd
145 Recognized values: principal.
146 See rpc.svcgssd(8) for details.
148 exportfs
151 Only debug= is recognized.
152
155 /etc/nfs.conf
156 Default NFS client configuration file
157 /etc/nfs.conf.d
159 When this directory exists and files ending with ".conf"
160 exist, those files will be used to set configuration vari‐
161 ables. These files will override variables set in
162 /etc/nfs.conf
163
165 nfsdcltrack(8), rpc.nfsd(8), rpc.mountd(8), nfsmount.conf(5).
166 NFS.CONF(5)