MirOS Manual: gai_strerror(3)

GAI_STRERROR(3)            BSD Programmer's Manual             GAI_STRERROR(3)


     gai_strerror - get error message string from EAI_xxx error code


     #include <sys/types.h>
     #include <sys/socket.h>
     #include <netdb.h>

     const char *
     gai_strerror(int ecode);


     The gai_strerror() function returns an error message string corresponding
     to the error code returned by getaddrinfo(3) or getnameinfo(3).

     The following error codes and their meaning are defined in <netdb.h>:

           EAI_ADDRFAMILY    address family for hostname not supported
           EAI_AGAIN         temporary failure in name resolution
           EAI_BADFLAGS      invalid value for ai_flags
           EAI_BADHINTS      invalid value for hints
           EAI_FAIL          non-recoverable failure in name resolution
           EAI_FAMILY        ai_family not supported.
           EAI_MEMORY        memory allocation failure
           EAI_NODATA        no address associated with hostname
           EAI_NONAME        hostname or servname not provided, or not known
           EAI_PROTOCOL      resolved protocol is unknown
           EAI_SERVICE       servname not supported for ai_socktype
           EAI_SOCKTYPE      ai_socktype not supported
           EAI_SYSTEM        system error returned in errno


     gai_strerror() returns a pointer to the error message string correspond-
     ing to ecode. If ecode is out of range, an implementation-specific error
     message string is returned.


     getaddrinfo(3), getnameinfo(3)

MirOS BSD #10-current         December 20, 2004                              1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.