HP-UX Reference (11i v1 00/12) - 3 Library Functions N-Z (vol 7)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

531

532

533

534

535

536

537

538

539

540

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man3/nan.3m

________________________________________________________________

___ ___

xdr_admin(3N) xdr_admin(3N)

rest of the current record in the stream, this routine returns TRUE if there is no more data in the

stream’s input buffer. It returns FALSE if there is additional data in the stream’s input buffer.

int xdrrec_readbytes()

This routine can be invoked only on streams created by xdrrec_create(). It attempts to read

nbytes bytes from the XDR stream into the buffer pointed to by addr. On success this routine returns

the number of bytes read, -1 on failure. A return value of 0 indicates an end of record.

bool_t xdrrec_skiprecord()

This routine can be invoked only on streams created by xdrrec_create() (see xdr_create(3N)). It

tells the XDR implementation that the rest of the current record in the stream’s input buffer should be

discarded. This routine returns TRUE if it succeeds, FALSE otherwise.

bool_t xdr_setpos()

A macro that invokes the set position routine associated with the XDR stream xdrs. The parameter

pos is a position value obtained from xdr_getpos() . This routine returns TRUE if the XDR

stream was repositioned, and FALSE otherwise.

Warning: it is difﬁcult to reposition some types of XDR streams, so this routine may fail with one type

of stream and succeed with another. Therefore, applications written for portability should not depend

on this feature.

unsigned long xdr_sizeof()

This routine returns the number of bytes required to encode data using the XDR ﬁlter function func,

excluding potential overhead such as RPC headers or record markers.

0 (zero) is returned on error.

This information might be used to select between transport protocols, or to determine the buffer size

for various lower levels of RPC client and server creation routines, or to allocate storage when XDR is

used outside of the RPC subsystem.

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 support

asynchronous cancellationor asynchronous signals.