svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
nfsmapid(8)
nfsmapid(8) System Administration Commands nfsmapid(8)
NAME
nfsmapid - NFS user and group id mapping daemon
SYNOPSIS
/usr/lib/nfs/nfsmapid
DESCRIPTION
The nfsmapid daemon maps to and from NFS version 4 owner and
owner_group identification attributes and local UID and GID numbers
used by both the NFS version 4 client and server.
nfsmapid uses the passwd and group entries in the /etc/nsswitch.conf
file to direct how it performs the mappings.
The nfsmapid daemon has no external, customer-accessible interfaces.
You can, however, administratively configure nfsmapid in one of the
following ways:
o Specify the nfsmapid_domain parameter in the SMF for NFS us‐
ing the sharectl(8) command.
o Specify the _nfsv4idmapdomain DNS resource record.
The currently selected NFSv4 domain is available in the file
/var/run/nfs4_domain.
Please refer to Managing Network File Systems in Oracle Solaris 11.4
for further details.
SMF Management
The nfsmapid service is managed by the service management facility,
smf(7), under the service identifier:
svc:/network/nfs/mapid
Administrative actions on this service, such as enabling, disabling, or
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command.
If it is disabled, it will be enabled by mount_nfs(8), share_nfs(8),
and automountd(8), unless its application/auto_enable property is set
to false.
nfsmapid caches a user's UID and GID. If a user subsequently changes a
UID or GID, using one of the utilities listed below, the nfsmapid cache
becomes stale. At this point, any NFS operation that gets or set at‐
tributes will result in the exchange of this stale information. To re‐
solve this situation, restart nfsmapid, as follows:
# svcadm restart svc:/network/nfs/mapid:default
The startup SMF parameter designating a domain name (nfsmapid_domain)
can be manipulated with the sharectl(8) command.
nfsmapid_domain
The setting for the NFS SMF parameter nfsmapid_domain overrides the
domain used by nfsmapid for building and comparing outbound and in‐
bound attribute strings, respectively. Also, this setting overrides
any other mechanism for setting the NFSv4 domain. In the absence of
a nfsmapid_domain setting, the nfsmapid daemon determines the NFSv4
domain as follows:
o If a properly configured /etc/resolv.conf (see re‐
solv.conf(5)) exists, nfsmapid queries specified name‐
server(s) for the domain.
o If a properly configured /etc/resolv.conf (see re‐
solv.conf(5)) exists, but the queried name server does
not have a proper record of the domain name, nfsmapid
attempts to obtain the domain name through the BIND in‐
terface (see resolver(3RESOLV)).
o If no /etc/resolv.conf exists, nfsmapid falls back on
using the configured domain name (see domainname(8)),
which is returned with the leading domain suffix re‐
moved. For example, for widgets.sales.example.com,
sales.example.com is returned.
o If /etc/resolv.conf does not exist, no domain name has
been configured (or no /etc/defaultdomain exists), nf‐
smapid falls back on obtaining the domain name from the
host name, if the host name contains a fully qualified
domain name (FQDN).
If a domain name is still not obtained following all of the preceding
steps, nfsmapid will have no domain configured. This results in the
following behavior:
o Outbound owner and owner_group attribute strings are encoded
as literal ID's. For example, the UID 12345 is encoded as
12345.
o nfsmapid ignores the domain portion of the inbound attribute
string and performs name service lookups only for the user
or group. If the user/group exists in the local system name
service databases, then the proper UID/GID will be mapped
even when no domain has been configured.
This behavior implies that the same administrative user/group domain
exists between NFSv4 client and server (that is, the same UID/GIDs for
users/groups on both client and server). In the case of overlapping ID
spaces, the inbound attribute string could potentially be mapped to the
wrong id. However, this is not functionally different from mapping the
inbound string to nobody, yet provides greater flexibility. See EXAM‐
PLES, below.
The utilities that allow you to change UID and GID are:
o usermod(8)
o userdel(8)
o groupmod(8)
o groupdel(8)
FILES
/var/run/nfs4_domain Contains the domain name currently used by
NFSv4.
EXAMPLES
Example 1 Setting Domain Name
The following command uses sharectl to set the domain name.
# sharectl set -p nfsmapid_domain=oracle.com nfs
The nfsmapid_domain property is described under NOTES, below.
Example 2 Obtaining Domain Name
The following command uses sharectl to obtain the current domain name.
# sharectl get -p nfsmapid_domain nfs nfsmapid_domain=oracle.com
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitysystem/file-system/nfs
SEE ALSO
svcs(1), resolver(3RESOLV), nfs(5), resolv.conf(5), attributes(7),
smf(7), automountd(8), domainname(8), groupdel(8), groupmod(8),
mount_nfs(8), share_nfs(8), sharectl(8), svcadm(8), userdel(8), user‐
mod(8)
NOTES
The nfsmapid daemon might not exist in a future release of Solaris.
Oracle Solaris 11.4 24 Jul 2020 nfsmapid(8)