rpcbind(3N)rpcbind(3N)NAME
rpcbind: rpcb_getmaps(), rpcb_getaddr(), rpcb_gettime(), rpcb_rmt‐
call(), rpcb_set(), rpcb_unset() - library routines for RPC bind ser‐
vice
SYNOPSISDESCRIPTION
These routines allow client C programs to make procedure calls to the
RPC binder service. (see rpcbind(1M)) maintains a list of mappings
between programs and their universal addresses.
Routines
An interface to the
service, which returns a list of the current RPC program-to-
address mappings on host. It uses the transport specified
through netconf to contact the remote service on host. This
routine will return if the remote could not be contacted.
An interface to the
service, which finds the address of the service on host that is
registered with program number prognum, version versnum, and
speaks the transport protocol associated with netconf. The
address found is returned in svcaddr. svcaddr should be preal‐
located. This routine returns if it succeeds. A return value
of means that the mapping does not exist or that the RPC system
failed to contact the remote service. In the latter case, the
global variable (see rpc_clnt_create(3N)) contains the RPC sta‐
tus.
This routine returns the time on
host in timep. If host is returns the time on its own machine.
This routine returns if it succeeds, if it fails. can be used
to synchronize the time between the client and the remote
server. This routine is particularly useful for secure RPC.
An interface to the
service, which instructs on host to make an RPC call on your
behalf to a procedure on that host. The structure should corre‐
spond to a connectionless transport. The parameter will be mod‐
ified to the server's address if the procedure succeeds (see and
in rpc_clnt_calls(3N) for the definitions of other parameters).
This procedure should normally be used for a and nothing else.
This routine allows programs to do lookup and call, all in one
step.
Note: Even if the server is not running, does not return any
error messages to the caller. In such a case, the caller times
out.
Note: is only available for connectionless transports.
An interface to the
service, which establishes a mapping between the triple
[prognum, versnum, and svcaddr on the machine's service. The
value of nc_netid must correspond to a network identifier that
is defined by the netconfig database. This routine returns if
it succeeds, otherwise. (See also in rpc_svc_calls(3N)). If
there already exists such an entry with will fail.
An interface to the
service, which destroys the mapping between the triple [prognum,
versnum, and the address on the machine's service. If netconf
is destroys all mapping between the triple [prognum, versnum,
all-transports] and the addresses on the machine's service.
This routine returns if it succeeds, otherwise. Only the owner
of the service or the super-user can destroy the mapping. (See
also 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 and before These functions should not
be called by a multithreaded application that supports asynchronous
cancellation or asynchronous signals.
SEE ALSOrpcbind(1M), rpcinfo(1M), rpc_clnt_calls(3N), rpc_svc_calls(3N).
rpcbind(3N)