rpcbind.3n (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

rpcbind(3N) rpcbind(3N)

connectionless transport. The parameter

*svcaddr will be modiﬁed to the server’s address if the

procedure succeeds (see

rpc_call() and clnt_call() in rpc_clnt_calls(3N) for the deﬁnitions

of other parameters).

This procedure should normally be used for a

ping and nothing else. This routine allows programs

to do lookup and call, all in one step.

Note: Even if the server is not running,

rpcbind does not return any error messages to the caller.

In such a case, the caller times out.

Note:

rpcb_rmtcall()

is only available for connectionless transports.

bool_t rpcb_set()

An interface to the rpcbind service, which establishes a mapping between the triple [prognum,

versnum , netconf

→nc_netid] and svcaddr on the machine’s

rpcbind service. The value of nc_netid

must correspond to a network identiﬁer that is deﬁned by the netconﬁg database. This routine

returns

TRUE if it succeeds, FALSE otherwise. (See also

svc_reg() in rpc_svc_calls(3N)). If

there already exists such an entry with

rpcbind

, rpcb_set() will fail.

bool_t rpcb_unset()

An interface to the rpcbind service, which destroys the mapping between the triple [prognum,

versnum , netconf

→nc_netid] and the address on the machine’s

rpcbind service. If netconf is

NULL,

rpcb_unset() destroys all mapping between the triple [prognum, versnum , all-transports] and

the addresses on the machine’s

rpcbind service. This routine returns

TRUE if it succeeds, FALSE

otherwise. Only the owner of the service or the super-user can destroy the mapping. (See also

svc_unreg() in rpc_svc_calls(3N)).

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 supports

asynchronous cancellation or asynchronous signals.