[Bug 1110331] Re: nscd no longer needs to be restarted by libc's resolvconf update script

[Thomas Hood]

There was recently a discussion on debian-devel about whether or not
programs using the resolver would deal properly with resolv.conf being
changed. I wrote a small program to illustrate that getaddrinfo() does
use the latest information in resolv.conf.

   http://lists.debian.org/debian-devel/2013/07/msg00227.html

(The discussion subsequently shifted onto another topic, namely, the
fact that getaddrinfo() has different return values on different OSes
and with different settings for nsswitch.conf "hosts:".)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1110331

Title:
  nscd no longer needs to be restarted by libc's resolvconf update
  script

Status in “resolvconf” package in Ubuntu:
  Confirmed

Bug description:
  Browsing the eglibc mailing list archives I notice[0] that the eglibc
  resolver has been enhanced[1] such that if /etc/resolv.conf's mtime
  changes then the client re-initializes the resolver state.

  This feature gives us an opportunity to eliminate from
  /etc/resolvconf/update.d/libc the code that restarts nscd after an
  alteration in resolv.conf. That would be a beneficial simplification.

  Possibly ditto for some other resolvconf update scripts.

  Can we take advantage of this eglibc enhancement in order to simplify
  resolvconf update scripts?  Do we want to?

  [0]http://www.eglibc.org/archives/patches/msg00977.html
  [1]http://patch-tracker.debian.org/patch/series/view/eglibc/2.11.3-4/any/submitted-resolv.conf-thread.diff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1110331/+subscriptions