public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "leolistas at solutti dot com dot br" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/5790] strange behavior of getnameinfo on multiple PTR records Date: Tue, 26 Feb 2008 13:31:00 -0000 [thread overview] Message-ID: <20080226133110.9913.qmail@sourceware.org> (raw) In-Reply-To: <20080225141520.5790.leolistas@solutti.com.br> ------- Additional Comments From leolistas at solutti dot com dot br 2008-02-26 13:31 ------- I dont know anything about coding .... but just as curiosity, the 2 IP addresses i listed, which contains 258 and 357 PTRs, have the following 'reply sizes': [root@correio postfix]# dig @ns1.cultura.com.br 58.255.34.201.in-addr.arpa ptr ;; Truncated, retrying in TCP mode. ;; Query time: 625 msec ;; SERVER: 201.34.255.2#53(201.34.255.2) ;; WHEN: Tue Feb 26 10:27:59 2008 ;; MSG SIZE rcvd: 9137 [root@correio postfix]# dig @ns1.cultura.com.br 70.255.34.201.in-addr.arpa ptr ;; Truncated, retrying in TCP mode. ;; Query time: 542 msec ;; SERVER: 201.34.255.2#53(201.34.255.2) ;; WHEN: Tue Feb 26 10:29:57 2008 ;; MSG SIZE rcvd: 12116 if i correctly understood, buffer would have to be raised to fit these kind of big replies, that's correct ? -- http://sourceware.org/bugzilla/show_bug.cgi?id=5790 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2008-02-26 13:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-25 14:16 [Bug libc/5790] New: " leolistas at solutti dot com dot br 2008-02-25 15:40 ` [Bug libc/5790] " jakub at redhat dot com 2008-02-26 13:31 ` leolistas at solutti dot com dot br [this message] 2008-03-04 15:26 ` drepper at redhat dot com [not found] <bug-5790-131@http.sourceware.org/bugzilla/> 2014-07-02 7:03 ` 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=20080226133110.9913.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).