nscd doesn't cache host entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eglibc (Ubuntu) |
Fix Released
|
Medium
|
Adam Conrad | ||
Precise |
Fix Released
|
Undecided
|
Adam Conrad | ||
Quantal |
Fix Released
|
Undecided
|
Adam Conrad |
Bug Description
[Impact / Justification]
For nscd users, the performance difference between a cached DNS lookup and a remote query can be anywhere from milliseconds to whole seconds, depending on the network and random luck. I've already verified here today that the concerns originally raised in the upstream bug have since been fixed, and Debian also dropped this patch a while ago, we just failed to sync with them when they did.
[Test Case]
As stated above, I've already tested that the actual root issue that led to the patch has been resolved, so the only thing to test is that the build binaries no longer have host caching disabled in the default /etc/nscd.conf
[Regression Potential]
Very low to non-existent. It's a single line change to a conffile, reverting a workaround that hasn't been needed in a long while.
[Original Report]
Binary package hint: nscd
Debian (and by implication Ubuntu) are the only distros to disable nscd hosts caching. In most cases, it is deployed with the expectation to mitigate expensive lookups (eg over VPN).
The bug cited [1] has been rejected by the core glibc developers three years ago as not a bug; all other distros (including Redhat EL and Novell SLES) have this functionality enabled. Why should we continue to penalise Ubuntu's performance any longer, in cases where nscd is deployed to improve performance?
Changed in eglibc (Ubuntu): | |
status: | Fix Committed → New |
tags: | added: patch |
description: | updated |
Changed in eglibc (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in eglibc (Ubuntu Precise): | |
assignee: | nobody → Adam Conrad (adconrad) |
Changed in eglibc (Ubuntu): | |
assignee: | nobody → Adam Conrad (adconrad) |
Changed in eglibc (Ubuntu Quantal): | |
assignee: | nobody → Adam Conrad (adconrad) |
upstream rejects the bug because "no program should have use gethostbyaddr*", but it's still a bug in every application that uses gethostbyaddr*. How can we make sure that we don't break those apps. How many apps in the archive are using gethostbyaddr*?