Date: Tue, 04 Oct 2011 20:56:38 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Samuel =?utf-8?Q?Mart=C3=ADn?= Moro <faust64@gmail.com> Cc: hackers@freebsd.org Subject: Re: Does anyone use nscd? Message-ID: <86botw4mc9.fsf@ds4.des.no> In-Reply-To: <CACuvv5HVC9mekJK1kpMinFbtA9NNmAbP-yYOU7F5ENSwwpEPyA@mail.gmail.com> ("Samuel =?utf-8?Q?Mart=C3=ADn?= Moro"'s message of "Tue, 4 Oct 2011 20:23:25 %2B0200") References: <86sjn84wco.fsf@ds4.des.no> <CACuvv5HVC9mekJK1kpMinFbtA9NNmAbP-yYOU7F5ENSwwpEPyA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Samuel Mart=C3=ADn Moro <faust64@gmail.com> writes: > Using it since a few, almost without any problem. Just one thing: > while connected to some external intranet, nscd still try to contact > my LDAP. Well, by default, nscd caches hits for an hour and misses for a minute. One could imagine an option to have nscd return the cached entry if it can't contact the server, even if it has technically expired, but the problem is that nscd doesn't know what the backend is and can't reliably tell whether the lookup failed because the server is unreachable or just because the entry does not exist; and even if it could, it would still have to query the backend every time, so you might still get a longish timeout for every lookup, depending on the type of backend and the reason it failed. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86botw4mc9.fsf>