https://bugzilla.novell.com/show_bug.cgi?id=441947 User pbaudis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=441947#c14 Petr Baudis <pbaudis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com Status|NEW |NEEDINFO Info Provider| |f.de.kruijf@hetnet.nl --- Comment #14 from Petr Baudis <pbaudis@novell.com> 2008-12-03 02:42:22 MST --- Are there any updates? Did you hit the bug again? Cc'ing Stephan: This was the only [*] known major issue around glibc-2.10. To sum up: With some broken nameservers, e.g. in some DSL modems, getaddrinfo() does not work, turning off IPv6 or using different nameservers works around the issue. This appeared to be fixed just before final glibc-2.10, but according to the latest reports (http://sourceware.org/bugzilla/show_bug.cgi?id=7060) this issue might still exist in final glibc-2.10. However, lack of bugreports against rc1 seems to indicate that this issue is not that widespread. Upstream is touching the resolver-related code again lately, but does not hint whether/which bugs that should fix and the communication is difficult as usual. I might try to look at this issue, but touching the resolver code might be risky. We could also just document the workaround in release notes, but it's hard to say if this will end up being a real issue. [*] Also, nscd is generally unstable. I've already fixed two bugs in nscd (unrelated to each other) but each time I fix a bug, it only means nscd runs long enough to uncover more. Since in 11.0, nscd wasn't stable either, I think it's fine to stabilize nscd in later updates, though the two bugs I have already fixed should be a major increase in stability. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.