3 More Discussions You Might Find Interesting
1. What is on Your Mind?
As strolling along this thread, what is on my mind I am still quite upset about the security guidelines set by the developers of Debian or any distro based upon Debian. For a while I have been really blissed using squeeze. No trouble at all with almost nothing, but using wheezy trouble came up with... (9 Replies)
Discussion started by: 1in10
9 Replies
2. Android
I'm about to make the switch over to Android OS for my mobile phone. I'm thinking my first Android phone might be something like a Samsung Galaxy S or an HTC Desire HD, or I might wait for one of the new Android tablets coming out later this year (like the Samsung 7" tablet on Android).
Was... (10 Replies)
Discussion started by: Neo
10 Replies
3. UNIX for Advanced & Expert Users
Are you a developer for Solaris products? If so, check this out: http://sdc.sun.com/solaris8/
The media kit that comes includes the entire media pack (Solaris 8) for both Intel and Sparc architectures, and a cool spill-proof coffe mug (for those all-nighters you're going to pull playing with... (1 Reply)
Discussion started by: LivinFree
1 Replies
LEARN ABOUT MOJAVE
rpcsvchost
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
