rpc_svc_err.3n (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

rpc_svc_err(3N) rpc_svc_err(3N)

NAME

rpc_svc_err: svcerr_auth(), svcerr_decode(), svcerr_noproc(), svcerr_noprog(), svcerr_progvers(),

svcerr_systemerr(), svcerr_weakauth() - library routines for server side remote procedure call errors

SYNOPSIS

#include <rpc/rpc.h>

void svcerr_auth(const SVCXPRT *

xprt , const enum auth_stat

why);

void svcerr_decode(const SVCXPRT *

xprt );

void svcerr_noproc(const SVCXPRT *

xprt );

void svcerr_noprog(const SVCXPRT *

xprt );

void svcerr_progvers(const SVCXPRT *

xprt ,

const rpcvers_t

low_vers , const rpcvers_t high_vers );

void svcerr_systemerr(const SVCXPRT *

xprt );

void svcerr_weakauth(const SVCXPRT *

xprt

);

DESCRIPTION

These routines are part of the RPC library which allows C language programs to make procedure calls on

other machines across the network.

These routines can be called by the server side dispatch function if there is any error in the transaction

with the client.

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.

Routines

See rpc (3N) for the deﬁnition of the

SVCXPRT data structure.

void svcerr_auth()

Called by a service dispatch routine that refuses to perform a remote procedure call due to an

authentication error.

void svcerr_decode()

Called by a service dispatch routine that cannot successfully decode the remote parameters (see

svc_getargs() in rpc_svc_reg (3N)).

void svcerr_noproc()

Called by a service dispatch routine that does not implement the procedure number that the caller

requests.

void svcerr_noprog()

Called when the desired program is not registered with the RPC package. Service implementors

usually do not need this routine.

void svcerr_progvers()

Called when the desired version of a program is not registered with the RPC package. low_vers is

the lowest version number, and high_vers is the highest version number. Service implementors usu-

ally do not need this routine.

void svcerr_systemerr()

Called by a service dispatch routine when it detects a system error not covered by any particular

protocol. For example, if a service can no longer allocate storage, it may call this routine.

void svcerr_weakauth()

Called by a service dispatch routine that refuses to perform a remote procedure call due to

insufﬁcient (but correct) authentication parameters. The routine calls svcerr_auth(xprt,

AUTH_TOOWEAK).

MULTITHREAD USAGE

Thread Safe: Yes

Cancel Safe: Yes

Fork Safe: No

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

Summary of content (2 pages)

PAGE 1
rpc_svc_err(3N) rpc_svc_err(3N) NAME rpc_svc_err: svcerr_auth(), svcerr_decode(), svcerr_noproc(), svcerr_noprog(), svcerr_progvers(), svcerr_systemerr(), svcerr_weakauth() - library routines for server side remote procedure call errors SYNOPSIS #include
PAGE 2
rpc_svc_err(3N) Async-cancel Safe: Async-signal Safe: rpc_svc_err(3N) No 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.