rpc.3n (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

rpc(3N) rpc(3N)

NAME

rpc - library routines for remote procedure calls

SYNOPSIS

cc [ ﬂag ]... ﬁle...

-lnsl [ library ]...

#include <rpc/rpc.h>

#include <netconfig.h>

DESCRIPTION

These routines allow C language programs to make procedure calls on other machines across a network.

First, the client sends a request to the server. On receipt of the request, the server calls a dispatch rou-

tine to perform the requested service, and then sends back a reply.

All RPC routines require the header

. Routines that take a netconfig structure also

require that

<netconfig.h>

be included. Applications using RPC and XDR routines should be linked

with the

libnsl library.

The HP-UX implementation of RPC only supports the X/Open Transport Interface (XTI). Applications

that are written using the Transport Layer Interface (TLI) and wish to use RPC, must convert their appli-

cation to XTI.

Multithread Considerations

In the case of multithreaded applications, the

_REENTRANT ﬂag must be deﬁned on the command line at

compilation time (

-D_REENTRANT). Deﬁning this ﬂag enables a thread-speciﬁc version of

rpc_createerr (see rpc_clnt_create(3N)).

When used in multithreaded applications, client-side routines are thread-safe. CLIENT handles (see

rpc_clnt_create(3N)) can be shared between threads; however, in this implementation requests by

different threads are serialized (that is, the ﬁrst request will receive its results before the second request

is sent).

When used in multithreaded applications, server-side routines are usually not thread-safe. In this imple-

mentation the service transport handle,

SVCXPRT (see rpc_svc_create(3N)), contains a single data area

for decoding arguments and encoding results. Therefore, this structure cannot be freely shared between

threads that call functions that do this. Routines that are affected by this restriction are marked as

unsafe for multithreaded applications (see rpc_svc_calls(3N)).

See the MULTITHREAD USAGE section of the routines’ respective manual pages.

Nettype

Some of the high-level RPC interface routines take a nettype string as one of the parameters (for example,

clnt_create(), svc_create(),

rpc_reg(), rpc_call()). This string deﬁnes a class of tran-

sports which can be used for a particular application.

nettype can be one of the following:

netpath Choose from the transports which have been indicated by their token names in the NET-

PATH environment variable. If NETPATH is unset or NULL, it defaults to visible.

netpath is the default nettype .

visible Choose the transports which have the visible ﬂag (v) set in the /etc/netconfig ﬁle.

circuit_v This is same as visible except that it chooses only the connection oriented transports

(semantics tpi_cots or tpi_cots_ord) from the entries in the /etc/netconfig

ﬁle.

datagram_v This is same as visible except that it chooses only the connectionless datagram tran-

sports (semantics tpi_clts) from the entries in the /etc/netconfig ﬁle.

circuit_n This is same as netpath except that it chooses only the connection oriented datagram

transports (semantics tpi_cots or tpi_cots_ord).

datagram_n This is same as netpath except that it chooses only the connectionless datagram tran-

sports (semantics tpi_clts).

udp This refers to Internet UDP.

tcp This refers to Internet TCP.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (6 pages)

PAGE 1
rpc(3N) rpc(3N) NAME rpc - library routines for remote procedure calls SYNOPSIS cc [ flag ]... file ... -lnsl [ library ]... #include #include DESCRIPTION These routines allow C language programs to make procedure calls on other machines across a network. First, the client sends a request to the server. On receipt of the request, the server calls a dispatch routine to perform the requested service, and then sends back a reply. All RPC routines require the header .
PAGE 2
rpc(3N) rpc(3N) If nettype is NULL, it defaults to netpath. The transports are tried in left to right order in the NETPATH variable or in top to down order in the /etc/netconfig file.
PAGE 3
rpc(3N) rpc(3N) * Created by individual implementations. * Client is responsible for initializing */ typedef struct { AUTH *cl_auth; struct clnt_ops { enum clnt_stat (*cl_call)(); void (*cl_abort)(); void (*cl_geterr)(); bool_t (*cl_freeres)(); void (*cl_destroy)(); bool_t (*cl_control)(); int (*cl_settimers)(); } *cl_ops; caddr_t cl_private; char *cl_netid; char *cl_tp; } CLIENT; auth.
PAGE 4
rpc(3N) rpcvers_t rpcproc_t struct opaque_auth caddr_t SVCXPRT rpc(3N) rq_vers; rq_proc; rq_cred; rq_clntcred; *rq_xprt; /* /* /* /* /* service protocol version */ the desired procedure */ raw creds from the wire */ read only cooked cred */ associated transport */ }; The XDR Structure /* * XDR operations. * XDR_ENCODE causes the type to be encoded into the stream. * XDR_DECODE causes the type to be extracted from the stream.
PAGE 5
rpc(3N) rpc(3N) Index to Routines The following table lists RPC routines and the manual reference pages on which they are described: RPC Routine Manual Reference Page auth_destroy authdes_create authdes_getucred authdes_seccreate authnone_create authsys_create authsys_create_default authunix_create authunix_create_default callrpc clnt_broadcast clnt_call clnt_control clnt_create clnt_create_timed clnt_create_vers clnt_create_vers_timed clnt_destroy clnt_dg_create clnt_freeres clnt_geterr clnt_pcreateerr
PAGE 6
rpc(3N) A svc_dg_create svc_dg_enablecache svc_fd_create svc_fds svc_freeargs svc_getargs svc_getcaller svc_getreq svc_getreqset svc_getrpccaller svc_raw_create svc_reg svc_register svc_run svc_sendreply svc_tli_create svc_tp_create svc_unreg svc_unregister svc_vc_create svcerr_auth svcerr_decode svcerr_noproc svcerr_noprog svcerr_progvers svcerr_systemerr svcerr_weakauth svcfd_create svcraw_create svctcp_create svcudp_bufcreate svcudp_create user2netname xdr_accepted_reply xdr_authsys_parms xdr_authunix_