Bug#42727: nscd doesn't respect /etc/resolv.conf changes
Hi,
>I think, nscd should respect changes of /etc/resolv.conf.
>At the moment it doesn't.
nscd will never respect changes of /etc/resolv.conf, because
it couldn't. nscd knows nothing about DNS, it caches
gethostbyname results which could also come from NIS, LDAP or
/etc/hosts. Since /etc/resolv.conf is loaded by NSS, nscd
couldn't do anythink. I thing /lib/libresolv.so should be
fixed to respect resolv.conf
>This is a problem with dialup links for example.
>I use nscd because the DNS cache - IMHO this makes sense
>in case of low-bandwidth links.
>Many ppp programs are modifying the /etc/resolv.conf
>to enable Dynamic DNS via PPP.
>
>At the moment my brute force solution is restarting the
>nscd but this cannot be a real solution.
Beside disabling the hosts cache it is the only solution
in the moment.
>And btw... Solaris nscd provides an command line option
> -i cachename
> Invalidate the specified cache.
>I guess, this might be a useful option for GNU nscd too.
This is implemented in the current glibc cvs archive.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE GmbH Schanzaeckerstr. 10 90443 Nuernberg
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.
Reply to: