Date: Mon, 29 Aug 2005 11:30:26 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Michael Bushkov <bushman@rsu.ru> Cc: Jacques Vidrine <nectar@freebsd.org>, freebsd-hackers@freebsd.org, Doug Barton <dougb@freebsd.org>, Brooks Davis <brooks@freebsd.org>, freebsd-current@freebsd.org Subject: Re: [PATCH] caching daemon release and nsswitch patches Message-ID: <20050829163025.GA25664@dan.emsphone.com> In-Reply-To: <20050829115740.N5409@stinger.cc.rsu.ru> References: <20050827170633.Y5409@stinger.cc.rsu.ru> <43123F3B.8070002@FreeBSD.org> <20050829115740.N5409@stinger.cc.rsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 29), Michael Bushkov said: > There is some information in my project's description here: > http://wikitest.freebsd.org/moin.cgi/NsswitchAndCachingTechnicalDetails One question that comes to mind: It looks like the end-user application is still responsible for performing nss lookups. How do you ensure that one user can't poison the cache and cause problems for other users? Could cached do all nss operations itself (making it more like nscd in other OSes)? -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050829163025.GA25664>