Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #382
Difficulty: Medium
HP-UX 11i V3 Release B.11.31 is registered as UNIX V7 compliant.
True or False?
Linux & Unix Commands - Search Man Pages

getrpcent_r(3) [bsd man page]

GETRPCENT_R(3)						     Linux Programmer's Manual						    GETRPCENT_R(3)

NAME
getrpcent_r, getrpcbyname_r, getrpcbynumber_r - get RPC entry (reentrant) SYNOPSIS
#include <netdb.h> int getrpcent_r(struct rpcent *result_buf, char *buf, size_t buflen, struct rpcent **result); int getrpcbyname_r(const char *name, struct rpcent *result_buf, char *buf, size_t buflen, struct rpcent **result); int getrpcbynumber_r(int number, struct rpcent *result_buf, char *buf, size_t buflen, struct rpcent **result); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): getrpcent_r(), getrpcbyname_r(), getrpcbynumber_r(): Since glibc 2.19: _DEFAULT_SOURCE Glibc 2.19 and earlier: _BSD_SOURCE || _SVID_SOURCE DESCRIPTION
The getrpcent_r(), getrpcbyname_r(), and getrpcbynumber_r() functions are the reentrant equivalents of, respectively, getrpcent(3), getr- pcbyname(3), and getrpcbynumber(3). They differ in the way that the rpcent structure is returned, and in the function calling signature and return value. This manual page describes just the differences from the nonreentrant functions. Instead of returning a pointer to a statically allocated rpcent structure as the function result, these functions copy the structure into the location pointed to by result_buf. The buf array is used to store the string fields pointed to by the returned rpcent structure. (The nonreentrant functions allocate these strings in static storage.) The size of this array is specified in buflen. If buf is too small, the call fails with the error ERANGE, and the caller must try again with a larger buffer. (A buffer of length 1024 bytes should be sufficient for most applications.) If the function call successfully obtains an RPC record, then *result is set pointing to result_buf; otherwise, *result is set to NULL. RETURN VALUE
On success, these functions return 0. On error, they return one of the positive error numbers listed in ERRORS. On error, record not found (getrpcbyname_r(), getrpcbynumber_r()), or end of input (getrpcent_r()) result is set to NULL. ERRORS
ENOENT (getrpcent_r()) No more records in database. ERANGE buf is too small. Try again with a larger buffer (and increased buflen). ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +--------------------+---------------+----------------+ |Interface | Attribute | Value | +--------------------+---------------+----------------+ |getrpcent_r(), | Thread safety | MT-Safe locale | |getrpcbyname_r(), | | | |getrpcbynumber_r() | | | +--------------------+---------------+----------------+ CONFORMING TO
These functions are GNU extensions. Functions with similar names exist on some other systems, though typically with different calling sig- natures. SEE ALSO
getrpcent(3), rpc(5) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-09-15 GETRPCENT_R(3)

Check Out this Related Man Page

GETRPCENT_R(3)						     Linux Programmer's Manual						    GETRPCENT_R(3)

NAME
getrpcent_r, getrpcbyname_r, getrpcbynumber_r - get RPC entry (reentrant) SYNOPSIS
#include <netdb.h> int getrpcent_r(struct rpcent *result_buf, char *buf, size_t buflen, struct rpcent **result); int getrpcbyname_r(const char *name, struct rpcent *result_buf, char *buf, size_t buflen, struct rpcent **result); int getrpcbynumber_r(int number, struct rpcent *result_buf, char *buf, size_t buflen, struct rpcent **result); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): getrpcent_r(), getrpcbyname_r(), getrpcbynumber_r(): Since glibc 2.19: _DEFAULT_SOURCE Glibc 2.19 and earlier: _BSD_SOURCE || _SVID_SOURCE DESCRIPTION
The getrpcent_r(), getrpcbyname_r(), and getrpcbynumber_r() functions are the reentrant equivalents of, respectively, getrpcent(3), getr- pcbyname(3), and getrpcbynumber(3). They differ in the way that the rpcent structure is returned, and in the function calling signature and return value. This manual page describes just the differences from the nonreentrant functions. Instead of returning a pointer to a statically allocated rpcent structure as the function result, these functions copy the structure into the location pointed to by result_buf. The buf array is used to store the string fields pointed to by the returned rpcent structure. (The nonreentrant functions allocate these strings in static storage.) The size of this array is specified in buflen. If buf is too small, the call fails with the error ERANGE, and the caller must try again with a larger buffer. (A buffer of length 1024 bytes should be sufficient for most applications.) If the function call successfully obtains an RPC record, then *result is set pointing to result_buf; otherwise, *result is set to NULL. RETURN VALUE
On success, these functions return 0. On error, they return one of the positive error numbers listed in ERRORS. On error, record not found (getrpcbyname_r(), getrpcbynumber_r()), or end of input (getrpcent_r()) result is set to NULL. ERRORS
ENOENT (getrpcent_r()) No more records in database. ERANGE buf is too small. Try again with a larger buffer (and increased buflen). ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +--------------------+---------------+----------------+ |Interface | Attribute | Value | +--------------------+---------------+----------------+ |getrpcent_r(), | Thread safety | MT-Safe locale | |getrpcbyname_r(), | | | |getrpcbynumber_r() | | | +--------------------+---------------+----------------+ CONFORMING TO
These functions are GNU extensions. Functions with similar names exist on some other systems, though typically with different calling sig- natures. SEE ALSO
getrpcent(3), rpc(5) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-09-15 GETRPCENT_R(3)

Featured Tech Videos