Premier IT Outsourcing and Support Services within the UK

User Tools

Site Tools


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


     getnetent_r,  getnetbyname_r, getnetbyaddr_r - get network entry (reen-


     #include <netdb.h>
     int getnetent_r(struct netent *result_buf, char *buf,
                     size_t buflen, struct netent **result,
                     int *h_errnop);
     int getnetbyname_r(const char *name,
                     struct netent *result_buf, char *buf,
                     size_t buflen, struct netent **result,
                     int *h_errnop);
     int getnetbyaddr_r(uint32_t net, int type,
                     struct netent *result_buf, char *buf,
                     size_t buflen, struct netent **result,
                     int *h_errnop);
 Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
     getnetent_r(), getnetbyname_r(), getnetbyaddr_r():
         Since glibc 2.19:
         Glibc 2.19 and earlier:
             _BSD_SOURCE || _SVID_SOURCE


     The getnetent_r(), getnetbyname_r(), and getnetbyaddr_r() functions are
     the  reentrant  equivalents  of,  respectively, getnetent(3), getnetby-
     name(3), and getnetbynumber(3).  They differ in the way that the netent
     structure is returned, and in the function calling signature and return
     value.  This manual page describes just the differences from  the  non-
     reentrant functions.
     Instead  of returning a pointer to a statically allocated netent struc-
     ture 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 netent 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  a  network  record,  then
     *result  is  set  pointing  to result_buf; otherwise, *result is set to
     The buffer pointed to by h_errnop is used  to  return  the  value  that
     would be stored in the global variable h_errno by the nonreentrant ver-
     sions of these functions.


     On success, these functions return 0.  On error, they return one of the
     positive error numbers listed in ERRORS.
     On error, record not found (getnetbyname_r(), getnetbyaddr_r()), or end
     of input (getnetent_r()) result is set to NULL.


     ENOENT (getnetent_r()) No more records in database.
     ERANGE buf is too small.  Try again with a larger buffer (and increased


     For   an   explanation   of   the  terms  used  in  this  section,  see
     allbox; lbw17 lb lb l l l.  Interface Attribute Value T{ getnetent_r(),
     getnetbyname_r(), getnetbyaddr_r() T}   Thread safety  MT-Safe locale


     These functions are GNU extensions.  Functions with similar names exist
     on some other systems, though typically with different  calling  signa-


     getnetent(3), networks(5)


     This  page  is  part of release 4.16 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

GNU 2017-09-15 GETNETENT_R(3)

/data/webs/external/dokuwiki/data/pages/man/getnetbyname_r.txt · Last modified: 2019/05/17 09:32 by

Was this page helpful?-11+1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki