rpcsvchost(8) [mojave man page]

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

NAME

     rpcsvchost -- hosting environment for DCE/RPC services

SYNOPSIS

     rpcsvchost [options] service [service ...]

DESCRIPTION

     rpcsvchost is a very simple environment for hosting DCE/RPC services.  It loads DCE/RPC services from the list of plugins given as arguments,
     binds to an appropriate set of endpoints and listens for protocol requests.

     If service is not a relative file name, it is assumed to be the name of a dylib located in /usr/lib/rpcsvc.

OPTIONS

     -debug, -nodebug
	      rpcsvchost will log debug information and may perform extra diagnostic checks. This option is typically only useful for debugging.

     -endpoints BINDING [,BINDING]
	      This argument specifies additional endpoints that rpcsvchost should attempt to bind.  BINDING must be a comma-separated list of
	      DCE/RPC binding strings that include both the protocol sequence and endpoint fields.

     -help    Prints a usage message and exits.

     -launchd, -nolaunchd
	      Normally, rpcsvchost attempts to bind all the well-known endpoints specified by the service plugins.  If there are no well-known
	      endpoints, it will bind new endpoints on all supported protocol sequences. The -launchd option disables this behavior and causes
	      rpcsvchost to check in with launchd(8) to obtain a set of sockets to bind as protocol endpoints.

	      Launchd sockets vended to rpcsvchost must be named with the appropriate DCE/RPC protocol sequence (eg. "ncacn_np").

     -sandbox, -nosandbox
	      When this option is specified, the modules loaded by rpcsvchost will be run in a sandbox.  rpcsvchost will attempt to intialize the
	      sandbox using the sandbox profile with the name com.apple.<module-name>.sb. See sandbox(7) for an overview of the sandbox facility.

     -register, -noregister
	      When this option is specified, rpcsvchost attempts to register the loaded services with the DCE/RPC endpoint mapper.

     -stdout  Causes rpcsvchost to print log messages to standard output instead of the system log.

     -wait-for-debugger
	      Causes rpcsvchost to wait for a debugger to attach after it has loaded and initialized its plugins. This is useful for debugging
	      instances of rpcsvchost that are launched by launchd(8).

DIAGNOSTICS

     The rpcsvchost utility exits 0 on success, and >0 if an error occurs.

SEE ALSO

     launchd.plist(5), launchd(8), sandbox(7)

HISTORY

     The rpcsvchost utility first appeared in Mac OS 10.7.

Darwin								   June 1, 2019 							    Darwin

RPC.LOCKD(8)						    BSD System Manager's Manual 					      RPC.LOCKD(8)

NAME

     rpc.lockd -- NFS file locking daemon

SYNOPSIS

     rpc.lockd [-d debug_level] [-g grace_period] [-x host_monitor_cache_period]

DESCRIPTION

     The rpc.lockd utility provides monitored and unmonitored file and record locking services in an NFS environment.  To monitor the status of
     hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8).

     The rpc.lockd utility runs whenever its services are needed to support either the NFS server (see nfsd(8)) or the NFS client (an NFS file
     system on which file locking requests have been made).  The daemon will remain running until a short time after its services are no longer
     needed to support either the NFS client or NFS server.  rpc.lockd will also make sure that the statd service (on which it depends) is run-
     ning.

     The following is a list of command line options that are available.  However, since rpc.lockd is normally started by launchd(8), configura-
     tion of these options should be controlled using the equivalent settings in the NFS configuration file.  See nfs.conf(5) for a list of tun-
     able parameters.

     -d      The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon.	These messages are
	     logged with level LOG_DEBUG and facility LOG_DAEMON.  Specifying a debug_level of 1 results in the generation of one log line per
	     protocol operation.  Higher debug levels can be specified, causing display of operation arguments and internal operations of the dae-
	     mon.

     -g      The -g option allows to specify the grace period (in seconds).  During the grace period rpc.lockd only accepts requests from hosts
	     which are reinitialising locks which existed before the server restart.  Default is 45 seconds.

     -x      The -x option tells rpc.lockd how long to cache state records for monitored hosts.  Setting it to zero will disable the cache which
	     will make lock and unlock requests from a single client more expensive because of additional interaction with the client's statd.
	     The default cache time is 60 seconds.

     Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON.

FILES

     /var/run/lockd.pid 	     The pid of the current lockd daemon.
     /System/Library/LaunchDaemons/com.apple.lockd.plist
				     The lockd service's property list file for launchd(8).
     /usr/include/rpcsvc/nlm_prot.x  RPC protocol specification for the network lock manager protocol.

SEE ALSO

     nfs.conf(5), rpc.statd(8), syslog(3), launchd(8)

BUGS

     The current implementation serialises locks requests that could be shared.

STANDARDS

     The implementation is based on the specification in "Protocols for X/Open PC Interworking: XNFS, Issue 4", X/Open CAE Specification C218,
     ISBN 1 872630 66 9.

HISTORY

     A version of rpc.lockd appeared in SunOS 4.

BSD
								  January 9, 2007							       BSD