On 11/5/20 12:49 PM, Florian Weimer wrote:
* Petr Menšík:
nscd has more usage downstream, leading to bugs such as:
<
https://bugzilla.redhat.com/show_bug.cgi?id=1551616>
I have very limited understanding of sssd principles. But I think it is
not comparable to nscd, which you just start or stop. No other
configuration is required.
Most of them are private, but you should be able to view them.
Yes, I can. Linked
bug references netgroup not cached, I cannot comment
it, know no additional information.
> Instead, I request again, split systemd-resolved into subpackage. I want
> it removed on my system and so do more people. Also, when I disable it,
> I have to fix /etc/resolv.conf by hand. I would think NetworkManager
> restart would refresh classic /etc/resolv.conf, like in F32.
This proposal is about nscd, not systemd-resolved.
systemd-resolved is mentioned in
the title and the body of proposal. So
it seems it is about it.
If Fedora chooses to adopt another local DNS cache, glibc will use that
(probably using the built-in nss_dns service module) systemd-resolved is
just what we have for now, so the proposal references it. But any other
DNS cache will work as well.
I do not think there is another cache like nscd, which
does not require
/etc/resolv.conf change or special nss hosts module. While I admit there
are more caches, I don't think any provides drop-in replacement.
Especially resolve nss plugin introduces so many (unannounced) changes,
I don't think it is a good alternative. Caching via dns module might be
more predictable even with systemd-resolved.
The hosts cache in nscd is arguably the weakest part of it, so
deprecating really shouldn't be controversial at all.
If you offer alternative,
which improves caching without additional
regressions, sure. I am not sure dnsmasq, systemd-resolved or unbound
can be compared to no configuration of nscd. Unlike other resolvers,
nscd caches only getaddrinfo calls, without ever touching outgoing DNS
client queries or /etc/resolv.conf modification. Is there any other
service able to do it?
Are there bugs I can help fixing, especially in hosts or ahosts databases?
--
Petr Menšík
Software Engineer
Red Hat,
http://www.redhat.com/
email: pemensik(a)redhat.com
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB