- server for NFS mount requests and NFS access checks
/usr/lib/nfs/mountd [-v] [-r]
mountd is an RPC server that answers requests for NFS access information and file system mount requests. It reads the file /etc/dfs/sharetab to determine which file systems are available for mounting by which remote machines. See sharetab(4). nfsd running on the local server will contact mountd the first time an NFS client tries to access the file system to determine whether the client should get read-write, read-only, or no access. This access can be dependent on the security mode used in the remoted procedure call from the client. See share_nfs(1M).
The command also provides information as to what file systems are mounted by which clients. This information can be printed using the showmount(1M) command.
The mountd daemon is automatically invoked by share(1M).
Only super user can run the mountd daemon.
Since mountd must be running for nfsd to function properly, mountd is automatically started by the svc:/network/nfs/server service.
Startup SMF parameters for mountd can be manipulated using the sharectl(1M) command. The currently supported parameters are:
The NFS client uses only NFS versions in the range specified by these variables. Valid values or versions are: 2, 3, and 4. By default, these variables are unspecified (commented out) and the client's default minimum is Version 2. The default maximum is version 4. You can override this range on a per-mount basis by using the -o vers= option to mount_nfs(1M).
The options shown below are supported for NVSv2/v3 clients. They are not supported for Solaris NFSv4 clients.
Reject mount requests from clients. Clients that have file systems mounted will not be affected.
Run the command in verbose mode. Each time mountd determines what access a client should get, it will log the result to the console, as well as how it got that result.
shared file system table
See attributes(5) for descriptions of the following attributes:
Some routines that compare hostnames use case-sensitive string comparisons; some do not. If an incoming request fails, verify that the case of the hostname in the file to be parsed matches the case of the hostname called for, and attempt the request again.