rpc_xdr(3N)rpc_xdr(3N)NAME
rpc_xdr: xdr_accepted_reply(), xdr_authsys_parms(), xdr_callhdr(),
xdr_callmsg(), xdr_opaque_auth(), xdr_rejected_reply(), xdr_replymsg()
- XDR library routines for remote procedure calls
SYNOPSISDESCRIPTION
These routines are used for describing the RPC messages in XDR lan‐
guage. They should normally be used by those who do not want to use
the RPC package directly.
Routines
See rpc(3N) for the definition of the data structure.
Used to translate between RPC
reply messages and their external representation. It includes
the status of the RPC call in the XDR language format. In the
case of success, it also includes the call results.
Used for describing UNIX operating system credentials.
It includes machine-name, uid, gid list, etc.
Used for describing RPC call header messages.
It encodes the static part of the call message header in the XDR
language format. It includes information such as transaction
ID, RPC version number, program, and version number.
Used for describing RPC call messages.
This includes all the RPC call information such as transaction
ID, RPC version number, program number, version number, authen‐
tication information, etc. This is normally used by servers to
determine information about the client RPC call.
Used for describing RPC opaque authentication information messages.
Used for describing RPC reply messages.
It encodes the rejected RPC message in the XDR language format.
The message could be rejected either because of version number
mis-match or because of authentication errors.
Used for describing RPC reply messages.
It translates between the RPC reply message and its external
representation. This reply could be either an acceptance,
rejection, or NULL.
MULTITHREAD USAGE
Thread Safe: Yes
Cancel Safe: Yes
Fork Safe: No
Async-cancel Safe: No
Async-signal Safe: No
These functions can be called safely in a multithreaded environment.
They may be cancellation points in that they call functions that are
cancel points.
In a multithreaded environment, these functions are not safe to be
called by a child process after and before These functions should not
be called by a multithreaded application that supports asynchronous
cancellation or asynchronous signals.
RETURN VALUE
These routines return if they succeed, otherwise.
SEE ALSOrpc(3N), xdr(3N).
rpc_xdr(3N)