#include <dce/dce_cf.h>void dce_cf_dced_entry_from_host( char *hostname, char **entry_name, error_status_t *status);
Possible status codes and their meanings are as follows:
The dce_cf_dced_entry_from_host() routine returns the name entered into the DCE namespace for a DCE host daemon (dced) on the host specified by the hostname parameter. If the hostname parameter is NULL, the dced name associated with the name returned by dce_cf_get_host_name() is returned. The string name is of the form /.:/hosts/hostname/config, and specifies the entry point into the dced namespace on the host. This is the location in the DCE namespace at which dced stores the objects associated with the host services it provides (the hostdata, srvrconf, srvrexec, secval, and keytab services, as well as ACL editing). It is also an actual name in the DCE namespace that you can import if you want to create your own RPC binding to dced.
You can use the dced entry name returned by this routine as input to the dced_binding_create() routine, input to sec_acl_* routines, or to rpc_ns_binding_import_* routines to establish a binding to a dced host service. If using dced_binding_create(), you append a service name to the entry returned by this routine. If using sec_acl_* routines, you append the service and the object name. If using rpc_ns_binding_import_*, you use only the entry returned by the routine.
You can also use the returned string to name objects that dced maintains, for example, when editing these objects' ACLs with dcecp. For example, the string name /.:/hosts/vineyard/config/srvrconf/dtsd names the server configuration data for the DTS server on the host vineyard.
No value is returned.
Functions: dce_cf_binding_entry_from_host(3dce), dce_cf_find_name_by_key(3dce), dce_cf_get_cell_name(3dce), dce_cf_get_host_name(3dce), dce_cf_prin_name_from_host(3dce), dced_binding_create(3dce).
Books: OSF DCE Application Development Guide--Core Components, Transarc DCE Command Reference.