|NFS.CONF(5)||File Formats Manual||NFS.CONF(5)|
nfs.conf - general configuration for NFS daemons and tools
This file contains site-specific configuration for various NFS daemons and other processes. Most configuration can also be passed to processes via command line arguments, but it can be more convenient to have a central file. In particular, this encourages consistent configuration across different processes.
When command line options are provided, they override values set in this file. When this file does not specify a particular parameter, and no command line option is provided, each tool provides its own default values.
The file format supports multiple sections, each of which can contain multiple value assignments. A section is introduced by a line containing the section name enclosed in square brackets, so
Any line starting with “#” or “;” is ignored, as is any blank line.
If the assigned value started with a “$” then the remainder is treated as a name and looked for in the section [environment] or in the processes environment (see environ(7)). The value found is used for this value.
The value name include is special. If a section contains
Lookup of section and value names is case-insensitive.
Where a Boolean value is expected, any of true, t, yes, y, on, or 1 can be used for "true", while false, f, no, n, off, or 0 can be used for "false". Comparisons are case-insensitive.
The following sections are known to various programs, and can contain the given named values. Most sections can also contain a debug value, which can be one or more from the list general, call, auth, parse, all. When a list is given, the members should be comma-separated. The values 0 and 1 are also accepted, with '0' making no changes to the debug level, and '1' equivalent to specifying 'all'.
See blkmapd(8), rpc.idmapd(8), and rpc.gssd(8) for details.
Setting rootdir to a valid path causes the nfs server to act as if the supplied path is being prefixed to all the exported entries. For instance, if rootdir=/my/root, and there is an entry in /etc/exports for /filesystem, then the client will be able to mount the path as /filesystem, but on the server, this will resolve to the path /my/root/filesystem.
See exportd(8) for details.
Note that setting "debug = auth" for exportd is equivalent to providing the --log-auth option.
The nfsdcltrack program is run directly by the Linux kernel and there is no opportunity to provide command line arguments, so the configuration file is the only way to configure this program. See nfsdcltrack(8) for details.
Version and protocol values are Boolean values as described above, and are also used by rpc.mountd. Threads and the two times are integers. port and rdma are service names or numbers. See rpc.nfsd(8) for details.
These, together with the protocol and version values in the [nfsd] section, are used to configure mountd. See rpc.mountd(8) for details.
Note that setting "debug = auth" for mountd is equivalent to providing the --log-auth option.
The state-directory-path value in the [mountd] section is also used by exportfs(8).
See rpc.statd(8) for details.
See rpc.statd(8) for details.
See sm-notify(8) for details.
See rpc.gssd(8) for details.
See rpc.svcgssd(8) for details.
See nfsrahead(5) for deatils.
nfsdcltrack(8), rpc.nfsd(8), rpc.mountd(8), nfsmount.conf(5).