OSF DCE Application Development Guide--Introduction and Style Guide

OSF DCE Application Development Guide—Introduction and Style Guide
/* Close the Object UUID-indexed database... */
DCE_SVC_DEBUG((smp_svc_handle, smp_s_server, svc_c_debug4,
"Calling dce_db_close()"));
dce_db_close(db_object, status);
if (*status != error_status_ok)
{
print_server_error("dce_db_close()", *status);
return;
}
/* Close the name-indexed database... */
DCE_SVC_DEBUG((smp_svc_handle, smp_s_server, svc_c_debug4,
"Calling dce_db_close()"));
dce_db_close(db_name, status);
if (*status != error_status_ok)
{
print_server_error("dce_db_close()", *status);
return;
}
DCE_SVC_DEBUG((smp_svc_handle, smp_s_server, svc_c_debug7,
"Exiting server_acl_mgr_close()"));
}
/******
*
* server_rdacl_export -- Make the rdacl interface available
* for ACL editors.
*
*
* Note that we don’t export to the namespace. Instead, the ACL editor
* will typically bind to the server via some other entry that holds
* the application-specific interface bindings. For our application,
* that entry is:
*
* /.:/sample_server_entry
*
* ...This entry (the "junction" to the object "entries") must hold at
* least one object UUID, and the same UUID must be put into the end-
* point map too. If not, ACL editors will have no way to distinguish
* the endpoints of this server from those of other servers on the same
* host that also export the rdacl interface.
*
* Called from main().
*
******/
A− 54 Tandem Computers Incorporated 124246