Date: Tue, 19 Aug 2014 14:54:40 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: "Eggert, Lars" <lars@netapp.com> Cc: Adam McDougall <mcdouga9@egr.msu.edu>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: nscd not caching Message-ID: <3B285476-A7ED-4C88-A2CB-9BD7E93C0E69@cs.huji.ac.il> In-Reply-To: <9C985132-212F-4F2D-BEBF-CFEAC0097CC9@netapp.com> References: <FA0C5D1E-780A-4B01-8513-5A4B77DA051D@netapp.com> <D86D34C6-B5E8-4141-BD9F-FF88B056DF6B@netapp.com> <53F0D3F3.4030804@egr.msu.edu> <9C985132-212F-4F2D-BEBF-CFEAC0097CC9@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 18, 2014, at 10:42 AM, Eggert, Lars <lars@netapp.com> wrote: > Hi, >=20 > On 2014-8-17, at 18:10, Adam McDougall <mcdouga9@egr.msu.edu> wrote: >> We were using +::::::::: type entries in the local password and group >> tables and I believe we used an unmodified /etc/nsswitch.conf = (excluding >> cache lines while testing nscd): >=20 > I tried that setup too, and it doesn't seem to be caching any NIS = lookups either. >=20 > The current NIS server is 25ms away, which is a pain. I'm trying to = get a local slave set up, which will make the need for nscd go away, but = it would sure be nice if it worked in the meantime. >=20 >> At our site, we never had enough load to outright require nscd on >> FreeBSD, although there were some areas where caching had a usability >> benefit. >=20 > Load is not an issue, latency is (see above). I know that this a bit late but have you ever considered Hesiod? it uses = DNS/txt. we have been using it since the days when BSDi had no NIS support and = haven=92t seen a ypserver not responding since :-) danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B285476-A7ED-4C88-A2CB-9BD7E93C0E69>