public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matz at suse dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nscd/13375] New: nscd inhibits HOSTALIASES envvar Date: Wed, 02 Nov 2011 15:36:00 -0000 [thread overview] Message-ID: <bug-13375-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13375 Bug #: 13375 Summary: nscd inhibits HOSTALIASES envvar Product: glibc Version: 2.14 Status: NEW Severity: normal Priority: P2 Component: nscd AssignedTo: drepper.fsp@gmail.com ReportedBy: matz@suse.de Classification: Unclassified Make sure nscd is running and indeed caching hosts database lookups (not the case with debian for instance), then: % HOSTALIASES=./fooalias strace getent hosts bla 2>&1 | grep fooalias shows that the file isn't accessed. It is accessed if nscd isn't running (and in that case is correctly interpreted). getent is just a convenient shorthand for a testcase, the gethostbyname interface behaves the same, i.e. doesn't lookup HOSTALIASES files when nscd is running. But according to the manpage it should. I think it's an extension, not POSIX behaviour, but one side needs to be fixed, either docu or code. FWIW, the environment variable isn't respected because res_hostalias isn't called, because __libc_res_nquery isn't called, because the nscd-accessing routines are called first. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-11-02 15:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-02 15:36 matz at suse dot de [this message] 2011-11-02 15:38 ` [Bug nscd/13375] " matz at suse dot de 2011-11-15 19:19 ` brian.cain at gmail dot com 2012-12-19 10:47 ` schwab@linux-m68k.org 2014-06-27 11:41 ` 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-13375-131@http.sourceware.org/bugzilla/ \ --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).