OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
interface or binding information.
One reason to create an empty server entry is to establish ownership of the entry. Server
entries are owned by the creator. If a server creates an entry, the server can also delete
the entry later. You can preempt such a circumstance by creating the entry yourself.
Later, the server exports its bindings to the existing server entry (provided that the ACL
allows this).
Use an rpcentry create operation to create an empty server entry as in the following,
which creates one named /.:/subsys/applications/bbs_server. The CDS directory
/.:/subsys/applications must already exist for this operation to succeed.
dcecp> rpcentry create /.:/subsys/applications/bbs_server
10.4.1.2 Deleting a Server Entry from CDS
Because server entries generally contain stable server binding information, they tend to
stay around rather than be deleted. Even when a server goes away for a short time, say,
overnight, it might not be practical to remove its entry. But when a server goes away for
a long time, you can avoid the client expense of trying to use the phantom server by
removing the server’s entry from CDS.
Use an rpcentry delete operation to remove a server entry from CDS as shown in the
following example:
dcecp> rpcentry delete /.:/subsys/applications/bbs_server
10.4.1.3 Exporting Binding Information to a Server Entry in CDS
Servers usually export their own binding information to CDS when they initialize or
when they are configured after installation. But sometimes, binding information may
have been removed for some reason or by accident and you want to restore it. Or another
transport has been added and you want to export the binding for the new transport.
You can manually export server binding information to a server entry by using an
rpcentry export operation. If the entry does not already exist, the rpcentry export
operation creates it provided the directory already exists and you have the necessary
permissions.
The following example illustrates exporting a server’s binding information to a server
entry named /.:/subsys/applications/bbs_server. The object UUID identifies the data
file resource used by bbs_server.
dcecp> rpcentry export /.:/subsys/applications/bbs_server \
-interface {458ffcbe-98c1-11cd-bd93-0000c08adf56 1.0} \
-binding {ncacn_ip_tcp 130.105.1.227} \
10 − 22 Tandem Computers Incorporated 124243