nfs4mapid(8) [mojave man page]

NFS4MAPID(8)						    BSD System Manager's Manual 					      NFS4MAPID(8)

NAME

     nfs4mapid -- shows NFSv4 mappings from uids or gids to over the wire string names and string names to uids or gids.

SYNOPSIS

     nfs4mapid [-G] string name
     nfs4mapid [-G] GUID
     nfs4mapid -u uid
     nfs4mapid -g gid

DESCRIPTION

     In the first form, nfs4mapid shows translations from NFSv4 string representations of users, and with the -G option, groups, to the corre-
     sponding local uids and gids.  In the second form shows the translations from opendirectoy GUIDS to NFSv4 strings. The well known strings
     names (which are distinguished by a trailing '@' ), such as "OWNER@" and "GROUP@" are represented locally by GUIDs and may not map to uids or
     gids. To map those GUIDS to NFSv4 strings use this form. The first form can be used to map the well known ids to GUIDs.  nfs4mapid does this
     by looking at the trailing '@' sign. Note that NFSv4 well known names are always groups and are used in ACEs.  In the third form, it shows
     the mapping from uids to the NFSv4 user@domain form.  Similarly, in the last form it shows the mapping from gids to the NFSv4 group@domain.
     nfs4mapid will also show the intermediate GUID translation if used. The NFSv4 domain name should be set with dscl(1).  See opendirectory(8)
     for instructions.

     -G      Map an NFSv4 string to a gid.

     -u      Map a uid to an NFSv4 user@domain string.

     -g      Map a gid to an NFSv4 group@domain string.

NOTES

     nfs4mapid uses a privileged nfs client system call to pass the translation request down to the kernel, so results will be the same as a
     request coming from an NFSv4 server. Because of this, nfs4mapid must be run with root privileges.

SEE ALSO

     dscl(1), nfs(5), opendirectoryd(8), mount_nfs(8),

HISTORY

     The nfs4mapid utility first appeared in OSX 10.10

BSD
								 February 20, 2014							       BSD

NFSUSERD(8)						    BSD System Manager's Manual 					       NFSUSERD(8)

NAME

     nfsuserd -- load user and group information into the kernel for NFSv4 services

SYNOPSIS

     nfsuserd [-domain domain_name] [-usertimeout minutes] [-usermax max_cache_size] [-verbose] [-force] [num_servers]

DESCRIPTION

     nfsuserd loads user and group information into the kernel for NFSv4.  It must be running for NFSv4 to function correctly, either client or
     server.

     Upon startup, it loads the machines DNS domain name, plus timeout and cache size limit into the kernel. It then preloads the cache with group
     and user information, up to the cache size limit and forks off N children (default 4), that service requests from the kernel for cache
     misses. The master server is there for the sole purpose of killing off the slaves.  To stop the nfsuserd, send a SIGUSR1 to the master
     server.

     The following options are available:

     -domain domain_name
	     This option allows you to override the default DNS domain name, which is acquired by taking either the suffix on the machine's host-
	     name or, if that name is not a fully qualified host name, the canonical name as reported by getaddrinfo(3).

     -usertimeout minutes
	     Overrides the default timeout for cache entries, in minutes. If the timeout is specified as 0, cache entries never time out. The
	     longer the time out, the better the performance, but the longer it takes for replaced entries to be seen. If your user/group database
	     management system almost never re-uses the same names or id numbers, a large timeout is recommended.  The default is 1 minute.

     -usermax max_cache_size
	     Overrides the default upper bound on the cache size. The larger the cache, the more kernel memory is used, but the better the perfor-
	     mance. If your system can afford the memory use, make this the sum of the number of entries in your group and password databases.
	     The default is 200 entries.

     -verbose
	     When set, the server logs a bunch of information to syslog.

     -force  This flag option must be set to restart the daemon after it has gone away abnormally and refuses to start, because it thinks nfsuserd
	     is already running.

     num_servers
	     Specifies how many servers to create (max 20).  The default of 4 may be sufficient. You should run enough servers, so that ps(1)
	     shows almost no running time for one or two of the slaves after the system has been running for a long period. Running too few will
	     have a major performance impact, whereas running too many will only tie up some resources, such as a process table entry and swap
	     space.

SEE ALSO

     getgrent(3), getpwent(3), nfsv4(4), group(5), passwd(5), nfsd(8)

HISTORY

     The nfsuserd utility was introduced with the NFSv4 experimental subsystem in 2009.

BUGS

     The nfsuserd use getgrent(3) and getpwent(3) library calls to resolve requests and will hang if the servers handling those requests fail and
     the library functions don't return. See group(5) and passwd(5) for more information on how the databases are accessed.

BSD
								  April 25, 2009							       BSD