On Mon, 29 Aug 2005, Dan Nelson wrote:
We can't ensure that, I guess. In the upcoming version (before the 1st of
September), the cache would be per-user. This would solve all the security
problems. In a little while, I'll implement the ability for cached to act
as nscd. So you'll be able to
Hi, Doug!
I'm not sure what guidelines were given to you when you started the project,
but in reviewing your work the first thing I noticed was that you are not
following the guidelines in the style(9) man page. You should read that page,
and spend an afternoon reformatting your code to fit
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
Michael Bushkov wrote:
Hi! I'm working on nsswitch improvement (during the Google Summer of
Code program.
First off, let me say that this is very exciting stuff! I'm particularly
excited about caching for the services stuff, as it will finally allow us to
bring in a more complete version of
Hi! I'm working on nsswitch improvement (during the Google Summer of Code
program. And, as the deadline is close, I'd like to make some kind of
release. Actually there would be 2 releases, this is the first.
This release includes 3 patches. They could be found in the Perforce
repository:
In the last episode (Aug 27), Michael Bushkov said:
Please try the patches and send me your feedback. I also hope that
there are no reasons not to merge changes, which were made to libc
(they are in include.diff and libc.diff) into the CURRENT. As for the
caching daemon (usr.sbin.diff patch) -
6 matches
Mail list logo
