rrpc_shutdown(3ncs) [ultrix man page]
rrpc_shutdown(3ncs) rrpc_shutdown(3ncs) Name rrpc_shutdown - shut down a server Syntax #include <idl/c/rrpc.h> void rrpc_$shutdown(handle, status) handle_t handle; status_$t *status; Arguments handle A remote procedure call (RPC) handle. status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it was success- ful. Description The routine shuts down a server, if the server allows it. A server can use the routine to allow or disallow remote shutdown. Diagnostics This section lists status codes for errors returned by this routine in rrpc_$shutdown_not_allowd You send an request to a server that has not issued an call. Restrictions On the client side, because of the way the calls are defined and implemented in the run-time library you must explicitly call into the entry point vector table for the interface to send an request across the network. The following is an example of a call that works as desired: (*rrpc_$client_epv.rrpc_$shutdown)(handle, &status); The server side stub routine calls the entry point on behalf of the client. The results of the call are then passed back to the client. Before making the shutdown call, the server must have previously executed the following call: rpc_$allow_remote_shutdown((unsigned long) TRUE,NULL,&status); If the server has not allowed remote shutdown, the call returns an status code. Files See Also intro(3ncs), rpc_allow_remote_shutdown(3ncs), rpc_shutdown(3ncs) rrpc_shutdown(3ncs)
Check Out this Related Man Page
rrpc_inq_stats(3ncs) rrpc_inq_stats(3ncs) Name rrpc_inq_stats - obtain statistics about a server Syntax #include <idl/c/rrpc.h> void rrpc_$inq_stats(handle, max_stats, stats, l_stat, status) handle_t handle; unsigned long max_stats; rrpc_$stat_vec_t stats; unsigned long *l_stat; status_$t *status; Arguments handle A remote procedure call (RPC) handle . max_stats The maximum number of elements in the array of statistics. stats An array of 32-bit integers representing statistics about the server. A set of rrpc_$sv constants defines indices for the ele- ments in this array. The following list describes the statistic indexed by each rrpc_$sv constant: rrpc_$sv_calls_in The number of calls processed by the server. rrpc_$sv_rcvd The number of packets received by the server. rrpc_$sv_sent The number of packets sent by the server. rrpc_$sv_calls_out The number of calls made by the server. rrpc_$sv_frag_resends The number of fragments sent by the server that duplicated previous sends. rrpc_$sv_dup_frags_rcvd The number of duplicate fragments received by the server. l_stat The index of the last element in the returned array. status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it was suc- cessful. Description The routine returns an array of integer statistics about a server. Restrictions On the client side, because of the way the calls are defined and implemented in the run-time library you must explicitly call into the entry point vector table for the interface to send an request across the network. The following is an example of a call that works as desired: (*rrpc_$client_epv.rrpc_$inq_stats)(handle, (unsigned long) max_stats, stats, &l_stat ,&status); The server sidestub routine calls the entry oint on behalf of the client. The results of the call are then passed back to the client. Files See Also intro(3ncs) rrpc_inq_stats(3ncs)