RPC Client Programs

· The dced daemon must run on any machine that has a DCE RPC server process that exports an interface with dynamic bindings. The dced daemon is used to register binding information (among other things. The dced daemon must run on every DCE machine because on every DCE machine there are client-side daemons that export interfaces. For example, the dtsd daemon exports the acl interface.

The dced daemon must be running before you configure any other DCE services because DCE services need to register their endpoints with dced. Only one dced daemon is needed on a machine. In fact, only one can run on a machine at a time because it uses a well-known port.

Network interfaces, routing services, and other network services must be available before DCE RPC starts. The dced daemon is started in the /etc/rc.dce file. The /etc/rc.dce file can be invoked by other rc files, such as /etc/rc and /etc/rc.local, so that DCE services can be brought up each time a machine boots.

· The DCE control program (dcecp) for the management and maintenance of the DCE RPC software. In addition, the rpccp program for operating on local registries. See DCE Administration Utilities for descriptions of both programs.