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 as‐
34 signed 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 in‐
49 cluded 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. The val‐
66 ues 0 and 1 are also accepted, with '0' making no changes to the debug
67 level, and '1' equivalent to specifying 'all'.
68 general
71 Recognized values: pipefs-directory.
72 See blkmapd(8), rpc.idmapd(8), and rpc.gssd(8) for details.
74 exports
77 Recognized values: rootdir.
78 Setting rootdir to a valid path causes the nfs server to act as
80 if the supplied path is being prefixed to all the exported en‐
81 tries. For instance, if rootdir=/my/root, and there is an entry
82 in /etc/exports for /filesystem, then the client will be able to
83 mount the path as /filesystem, but on the server, this will re‐
84 solve to the path /my/root/filesystem.
85 exportd
88 Recognized values: threads, cache-use-upaddr, ttl, state-direc‐
89 tory-path
90 See exportd(8) for details.
92 Note that setting "debug = auth" for exportd is equivalent to
94 providing the --log-auth option.
95 nfsdcltrack
98 Recognized values: storagedir.
99 The nfsdcltrack program is run directly by the Linux kernel and
101 there is no opportunity to provide command line arguments, so
102 the configuration file is the only way to configure this pro‐
103 gram. See nfsdcltrack(8) for details.
104 nfsd Recognized values: threads, host, scope, port, grace-time,
107 lease-time, udp, tcp, vers3, vers4, vers4.0, vers4.1, vers4.2,
108 rdma,
109 Version and protocol values are Boolean values as described
111 above, and are also used by rpc.mountd. Threads and the two
112 times are integers. port and rdma are service names or numbers.
113 See rpc.nfsd(8) for details.
114 mountd Recognized values: manage-gids, descriptors, port, threads, re‐
117 verse-lookup, cache-use-upaddr, ttl, state-directory-path, ha-
118 callout.
119 These, together with the protocol and version values in the
121 [nfsd] section, are used to configure mountd. See rpc.mountd(8)
122 for details.
123 Note that setting "debug = auth" for mountd is equivalent to
125 providing the --log-auth option.
126 The state-directory-path value in the [mountd] section is also
128 used by exportfs(8).
129 statd Recognized values: port, outgoing-port, name, state-directory-
132 path, ha-callout.
133 See rpc.statd(8) for details.
135 lockd Recognized values: port and udp-port.
138 See rpc.statd(8) for details.
140 sm-notify
143 Recognized values: retry-time, outgoing-port, and outgoing-addr.
144 See sm-notify(8) for details.
146 gssd Recognized values: verbosity, rpc-verbosity, use-memcache, use-
149 machine-creds, use-gss-proxy, avoid-dns, limit-to-legacy-enc‐
150 types, context-timeout, rpc-timeout, keytab-file, cred-cache-di‐
151 rectory, preferred-realm, set-home.
152 See rpc.gssd(8) for details.
154 svcgssd
157 Recognized values: principal.
158 See rpc.svcgssd(8) for details.
160 exportfs
163 Only debug= is recognized.
164 nfsrahead
167 Recognized values: nfs, nfsv4, default.
168 See nfsrahead(5) for deatils.
170
173 /etc/nfs.conf
174 Default NFS client configuration file
175 /etc/nfs.conf.d
177 When this directory exists and files ending with ".conf" ex‐
178 ist, those files will be used to set configuration variables.
179 These files will override variables set in /etc/nfs.conf
180
182 nfsdcltrack(8), rpc.nfsd(8), rpc.mountd(8), nfsmount.conf(5).
183 NFS.CONF(5)