from small one page howto to huge articles all in one place

search text in:




Other .linuxhowtos.org sites:gentoo.linuxhowtos.org



Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

210209

userrating:


May 25th. 2007:
Words

486

Views

259175

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

150544

userrating:


April, 26th. 2006:

Druckversion
You are here: manpages





getrpcent_r

Section: C Library Functions (3)
Updated: 202-0-28
Index Return to Main Contents
 

NAME

getrpcent_r, getrpcbyname_r, getrpcbynumber_r - get RPC entry (reentrant)  

LIBRARY

Standard C library (libc,~-lc)  

SYNOPSIS

#include <netdb.h>
int getrpcent_r(size_t size;
                struct rpcent *result_buf, char buf[size],
                size_t size, struct rpcent **result);
int getrpcbyname_r(size_t size;
                const char *name,
                struct rpcent *result_buf, char buf[size],
                size_t size, struct rpcent **result);
int getrpcbynumber_r(size_t size;
                int number,
                struct rpcent *result_buf, char buf[size],
                size_t size, 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), getrpcbyname(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 size. 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 size 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 size).
 

ATTRIBUTES

For an explanation of the terms used in this section, see attributes(7).
InterfaceAttributeValue
getrpcent_r(), getrpcbyname_r(), getrpcbynumber_r() Thread safetyM-Safe locale
 

VERSIONS

Functions with similar names exist on some other systems, though typically with different calling signatures.  

STANDARDS

GNU.  

SEE ALSO

getrpcent(3), rpc(5)


 

Index

NAME
LIBRARY
SYNOPSIS
DESCRIPTION
RETURN VALUE
ERRORS
ATTRIBUTES
VERSIONS
STANDARDS
SEE ALSO





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2025 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 14.9 ms