United States-English |
|
|
HP-UX Reference > Rrpc_svc_err(3N)HP-UX 11i Version 3: February 2007 |
|
NAMErpc_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); DESCRIPTIONThese 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 application to XTI. RoutinesSee rpc(3N) for the definition of the SVCXPRT data structure.
MULTITHREAD USAGE
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. |
Printable version | ||
|