⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 tcpip-manpages.sgml

📁 ecos实时嵌入式操作系统
💻 SGML
📖 第 1 页 / 共 5 页
字号:
     EAI_MEMORY         There was a memory allocation failure.     EAI_NONAME         The name does not resolve for the supplied parameters.                        NI_NAMEREQD is set and the host's name cannot be                        located, or both nodename and servname were null.     EAI_SYSTEM         A system error occurred.  The error code can be found                        in errno.SEE ALSO     getaddrinfo(3), gethostbyaddr(3), getservbyport(3), hosts(5),     resolv.conf(5), services(5), hostname(7), named(8)     R. Gilligan, S. Thomson, J. Bound, and W. Stevens, Basic Socket Interface     Extensions for IPv6, RFC2553, March 1999.     Tatsuya Jinmei and Atsushi Onoe, An Extension of Format for IPv6 Scoped     Addresses, internet draft, draft-ietf-ipngwg-scopedaddr-format-02.txt,     work in progress material.     Craig Metz, "Protocol Independence Using the Sockets API", Proceedings of     the freenix track: 2000 USENIX annual technical conference, June 2000.HISTORY     The implementation first appeared in WIDE Hydrangea IPv6 protocol stack     kit.STANDARDS     The getaddrinfo() function is defined IEEE POSIX 1003.1g draft specifica-     tion, and documented in ``Basic Socket Interface Extensions for IPv6''     (RFC2553).BUGS     The current implementation is not thread-safe.     The text was shamelessly copied from RFC2553.     OpenBSD intentionally uses different NI_MAXHOST value from what RFC2553     suggests, to avoid buffer length handling mistakes.BSD                              May 25, 1995                              BSD    </screen>  </sect1>  <sect1 id="net-common-tcpip-manpages-getnetent">    <title>getnetent</title>    <screen>GETNETENT(3)            System Library Functions Manual           GETNETENT(3)NAME     getnetent, getnetbyaddr, getnetbyname, setnetent, endnetent - get network     entrySYNOPSIS     #include &lt;netdb.h>     struct netent *     getnetent(void);     struct netent *     getnetbyname(char *name);     struct netent *     getnetbyaddr(in_addr_t net, int type);     void     setnetent(int stayopen);     void     endnetent(void);DESCRIPTION     The getnetent(), getnetbyname(), and getnetbyaddr() functions each return     a pointer to an object with the following structure containing the bro-     ken-out fields of a line in the network database, /etc/networks.           struct  netent {                   char            *n_name;        /* official name of net */                   char            **n_aliases;    /* alias list */                   int             n_addrtype;     /* net number type */                   in_addr_t       n_net;          /* net number */           };     The members of this structure are:     n_name      The official name of the network.     n_aliases   A zero-terminated list of alternate names for the network.     n_addrtype  The type of the network number returned; currently only                 AF_INET.     n_net       The network number.  Network numbers are returned in machine                 byte order.     The getnetent() function reads the next line of the file, opening the     file if necessary.     The setnetent() function opens and rewinds the file.  If the stayopen     flag is non-zero, the net database will not be closed after each call to     getnetbyname() or getnetbyaddr().     The endnetent() function closes the file.     The getnetbyname() and getnetbyaddr() functions search the domain name     server if the system is configured to use one.  If the search fails, or     no name server is configured, they sequentially search from the beginning     of the file until a matching net name or net address and type is found,     or until EOF is encountered.  Network numbers are supplied in host order.FILES     /etc/networksDIAGNOSTICS     Null pointer (0) returned on EOF or error.SEE ALSO     resolver(3), networks(5)HISTORY     The getnetent(), getnetbyaddr(), getnetbyname(), setnetent(), and     endnetent() functions appeared in 4.2BSD.BUGS     The data space used by these functions is static; if future use requires     the data, it should be copied before any subsequent calls to these func-     tions overwrite it.  Only Internet network numbers are currently under-     stood.  Expecting network numbers to fit in no more than 32 bits is     naive.BSD                             March 13, 1997                             BSD    </screen>  </sect1>  <sect1 id="net-common-tcpip-manpages-getprotoent">    <title>getprotoent</title>    <screen>GETPROTOENT(3)          System Library Functions Manual         GETPROTOENT(3)NAME     getprotoent, getprotobynumber, getprotobyname, setprotoent, endprotoent -     get protocol entrySYNOPSIS     #include &lt;netdb.h>     struct protoent *     getprotoent(void);     struct protoent *     getprotobyname(char *name);     struct protoent *     getprotobynumber(int proto);     void     setprotoent(int stayopen);     void     endprotoent(void);DESCRIPTION     The getprotoent(), getprotobyname(), and getprotobynumber() functions     each return a pointer to an object with the following structure contain-     ing the broken-out fields of a line in the network protocol database,     /etc/protocols.           struct  protoent {                   char    *p_name;        /* official name of protocol */                   char    **p_aliases;    /* alias list */                   int     p_proto;        /* protocol number */           };     The members of this structure are:     p_name     The official name of the protocol.     p_aliases  A zero-terminated list of alternate names for the protocol.     p_proto    The protocol number.     The getprotoent() function reads the next line of the file, opening the     file if necessary.     The setprotoent() function opens and rewinds the file.  If the stayopen     flag is non-zero, the net database will not be closed after each call to     getprotobyname() or getprotobynumber().     The endprotoent() function closes the file.     The getprotobyname() and getprotobynumber() functions sequentially search     from the beginning of the file until a matching protocol name or protocol     number is found, or until EOF is encountered.RETURN VALUES     Null pointer (0) returned on EOF or error.FILES     /etc/protocolsSEE ALSO     protocols(5)HISTORY     The getprotoent(), getprotobynumber(), getprotobyname(), setprotoent(),     and endprotoent() functions appeared in 4.2BSD.BUGS     These functions use a static data space; if the data is needed for future     use, it should be copied before any subsequent calls overwrite it.  Only     the Internet protocols are currently understood.BSD                              June 4, 1993                              BSD    </screen>  </sect1>  <sect1 id="net-common-tcpip-manpages-getrrsetbyname">    <title>getrrsetbyname</title>    <screen>GETRRSETBYNAME(3)       System Library Functions Manual      GETRRSETBYNAME(3)NAME     getrrsetbyname - retrieve DNS recordsSYNOPSIS     #include &lt;netdb.h>     int     getrrsetbyname(const char *hostname, unsigned int rdclass,             unsigned int rdtype, unsigned int flags, struct rrsetinfo **res);     int     freerrset(struct rrsetinfo **rrset);DESCRIPTION     getrrsetbyname() gets a set of resource records associated with a     hostname, class and type.  hostname is a pointer a to null-terminated     string.  The flags field is currently unused and must be zero.     After a successful call to getrrsetbyname(), *res is a pointer to an     rrsetinfo structure, containing a list of one or more rdatainfo struc-     tures containing resource records and potentially another list of     rdatainfo structures containing SIG resource records associated with     those records.  The members rri_rdclass and rri_rdtype are copied from     the parameters.  rri_ttl and rri_name are properties of the obtained     rrset.  The resource records contained in rri_rdatas and rri_sigs are in     uncompressed DNS wire format.  Properties of the rdataset are represented     in the rri_flags bitfield. If the RRSET_VALIDATED bit is set, the data     has been DNSSEC validated and the signatures verified.     The following structures are used:     struct  rdatainfo {             unsigned int            rdi_length;     /* length of data */             unsigned char           *rdi_data;      /* record data */     };     struct  rrsetinfo {             unsigned int            rri_flags;      /* RRSET_VALIDATED ... */             unsigned int            rri_rdclass;    /* class number */             unsigned int            rri_rdtype;     /* RR type number */             unsigned int            rri_ttl;        /* time to live */             unsigned int            rri_nrdatas;    /* size of rdatas array */             unsigned int            rri_nsigs;      /* size of sigs array */             char                    *rri_name;      /* canonical name */             struct rdatainfo        *rri_rdatas;    /* individual records */             struct rdatainfo        *rri_sigs;      /* individual signatures */     };     All of the information returned by getrrsetbyname() is dynamically allo-     cated: the rrsetinfo and rdatainfo structures, and the canonical host     name strings pointed to by the rrsetinfostructure. Memory allocated for     the dynamically allocated structures created by a successful call to     getrrsetbyname() is released by freerrset().  rrset is a pointer to a     struct rrset created by a call to getrrsetbyname().     If the EDNS0 option is activated in resolv.conf(3), getrrsetbyname() will     request DNSSEC authentication using the EDNS0 DNSSEC OK (DO) bit.RETURN VALUES     getrrsetbyname() returns zero on success, and one of the following error     codes if an error occurred:     ERRSET_NONAME    the name does not exist     ERRSET_NODATA    the name exists, but does not have data of the desired                      type     ERRSET_NOMEMORY  memory could not be allocated     ERRSET_INVAL     a parameter is invalid     ERRSET_FAIL      other failureSEE ALSO     resolver(3), resolv.conf(5), named(8)AUTHORS     Jakob Schlyter &lt;jakob@openbsd.org>HISTORY     getrrsetbyname() first appeared in OpenBSD 3.0.  The API first appeared     in ISC BIND version 9.BUGS     The data in *rdi_data should be returned in uncompressed wire format.     Currently, the data is in compressed format and the caller can't uncom-     press since it doesn't have the full message.CAVEATS     The RRSET_VALIDATED flag in rri_flags is set if the AD (autenticated     data) bit in the DNS answer is set. This flag should not be trusted     unless the transport between the nameserver and the resolver is secure     (e.g. IPsec, trusted network, loopback communication).BSD                              Oct 18, 2000                              BSD    </screen>  </sect1>  <sect1 id="net-common-tcpip-manpages-getservent">    <title>getservent</title>    <screen>GETSERVENT(3)           System Library Functions Manual          GETSERVENT(3)NAME     getservent, getservbyport, getservbyname, setservent, endservent - get     service entrySYNOPSIS     #include &lt;netdb.h>     struct servent *     getservent(void);     struct servent *     getservbyname(char *name, char *proto);     struct servent *     getservbyport(int port, char *proto);

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -