Re: [PATCH] caching daemon release and nsswitch patches
From: Dan Nelson (dnelson_at_allantgroup.com)
Date: 08/29/05
- Previous message: Scott Long: "Re: Syscall/Sysret state on i386 arch"
- In reply to: Michael Bushkov: "Re: [PATCH] caching daemon release and nsswitch patches"
- Next in thread: Michael Bushkov: "Re: [PATCH] caching daemon release and nsswitch patches"
- Reply: Michael Bushkov: "Re: [PATCH] caching daemon release and nsswitch patches"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 29 Aug 2005 11:30:26 -0500 To: Michael Bushkov <bushman@rsu.ru>
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 _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: Scott Long: "Re: Syscall/Sysret state on i386 arch"
- In reply to: Michael Bushkov: "Re: [PATCH] caching daemon release and nsswitch patches"
- Next in thread: Michael Bushkov: "Re: [PATCH] caching daemon release and nsswitch patches"
- Reply: Michael Bushkov: "Re: [PATCH] caching daemon release and nsswitch patches"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]