public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kurt at roeckx dot be" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/15726] New: getaddrinfo() error codes Date: Wed, 10 Jul 2013 18:04:00 -0000 [thread overview] Message-ID: <bug-15726-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15726 Bug ID: 15726 Summary: getaddrinfo() error codes Product: glibc Version: 2.17 Status: NEW Severity: normal Priority: P2 Component: network Assignee: unassigned at sourceware dot org Reporter: kurt at roeckx dot be There have been many changes in the return values from getaddrinfo() in glibc to the point I can't rely on the return values to mean anything. As far as I know the standard for this is rfc3493 (also known as 2553bis). I'm going to quote those that I'm having a problem with as glibc now returns: [EAI_AGAIN] The name could not be resolved at this time. Future attempts may succeed. [EAI_FAIL] A non-recoverable error occurred when attempting to resolve the name. [EAI_NONAME] The name does not resolve for the supplied parameters. Neither nodename nor servname were supplied. At least one of these must be supplied. And from the manpage: EAI_AGAIN The name server returned a temporary failure indication. Try again later. EAI_FAIL The name server returned a permanent failure indication. EAI_NONAME The node or service is not known; or both node and service are NULL; or AI_NUMERICSERV was specified in hints.ai_flags and service was not a numeric port-number string. What I expect: - Things work as expected: return 0 - The nameserver replies that the hostname does not exist: EAI_FAIL - The nameserver doesn't reply, or replies with a temporary failure: EAI_AGAIN - You used AI_NUMERICHOST or AI_NUMERICSERV and didn't give a number: EAI_NONAME What I think the current situation is: - Things work as expected: return 0 - The nameserver replies that the hostname does not exist: EAI_NONAME - The nameserver doesn't reply: EAI_NONAME - The nameserver replies with a temporary failure: EAI_NONAME Kurt -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-07-10 18:04 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-10 18:04 kurt at roeckx dot be [this message] 2013-07-10 21:15 ` [Bug network/15726] " schwab@linux-m68k.org 2013-07-10 21:35 ` kurt at roeckx dot be 2013-07-10 21:44 ` schwab@linux-m68k.org 2013-07-10 21:45 ` kurt at roeckx dot be 2013-07-11 10:04 ` [Bug network/15726] getaddrinfo() returns incorrect status jdthood at gmail dot com 2013-07-11 13:27 ` zackw at panix dot com 2013-07-11 13:37 ` jdthood at gmail dot com 2013-07-11 16:54 ` kurt at roeckx dot be 2013-07-12 10:03 ` jdthood at gmail dot com 2013-07-14 16:08 ` bugdal at aerifal dot cx 2013-07-18 7:05 ` carlos at redhat dot com 2013-07-18 14:58 ` bugdal at aerifal dot cx 2013-07-18 17:45 ` carlos at redhat dot com 2013-07-30 7:05 ` jdthood at gmail dot com 2013-07-30 7:16 ` siddhesh at redhat dot com 2013-07-30 12:07 ` bugdal at aerifal dot cx 2013-07-31 4:08 ` carlos at redhat dot com 2013-08-09 14:35 ` kurt at roeckx dot be 2013-08-09 16:05 ` carlos at redhat dot com 2013-08-13 15:38 ` kurt at roeckx dot be 2013-08-13 19:25 ` carlos at redhat dot com 2013-08-24 18:08 ` kurt at roeckx dot be 2013-08-28 4:53 ` carlos at redhat dot com 2013-08-28 9:04 ` bugdal at aerifal dot cx 2013-08-28 21:20 ` kurt at roeckx dot be 2013-08-30 1:10 ` bugdal at aerifal dot cx 2013-08-30 7:11 ` kurt at roeckx dot be 2013-09-01 0:46 ` jdthood at gmail dot com 2013-09-01 2:11 ` jdthood at gmail dot com 2014-03-20 16:51 ` jdthood at gmail dot com 2014-03-21 11:26 ` jdthood at gmail dot com 2014-06-13 13:24 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15726-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).