HP-UX Reference (11i v2 03/08) - 3 Library Functions N-Z (vol 7)

rpc_clnt_calls(3N) rpc_clnt_calls(3N)

the procedure’s results; in is the address of the procedure’s argument(s), and out is the address of

where to place the result(s). nettype can be any of the values listed on rpc(3N). This routine

returns

RPC_SUCCESS if it succeeds, or an appropriate status is returned. Use the

clnt_perrno() routine to translate failure status into error messages.

Warning:

rpc_call() uses the ﬁrst available transport belonging to the class nettype , on which it

can create a connection. You do not have control of timeouts or authentication using this routine.

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

fork()

and before exec(). These functions should not be called by a multithreaded application that support

asynchronous cancellation or asynchronous signals.