** Changed in: resolvconf (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
Fix Released
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
