public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matthias dot andree at gmx dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3675] libc caches resolv.conf forever Date: Thu, 07 Dec 2006 15:22:00 -0000 [thread overview] Message-ID: <20061207152219.8112.qmail@sourceware.org> (raw) In-Reply-To: <20061207143827.3675.matthias.andree@gmx.de> ------- Additional Comments From matthias dot andree at gmx dot de 2006-12-07 15:22 ------- Thank you. Could you confirm that res_init() does: - *not* look at the RES_INIT state (i. e. re-reads resolv.conf every time it is called), and - *not* leak memory when called frequently? -- http://sourceware.org/bugzilla/show_bug.cgi?id=3675 ------- 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:[~2006-12-07 15:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-07 14:38 [Bug libc/3675] New: " matthias dot andree at gmx dot de 2006-12-07 15:17 ` [Bug libc/3675] " drepper at redhat dot com 2006-12-07 15:22 ` matthias dot andree at gmx dot de [this message] [not found] <bug-3675-131@http.sourceware.org/bugzilla/> 2015-05-15 20:37 ` 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=20061207152219.8112.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).