Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Jun 2003 09:58:11 +0400
From:      Michael Bushkov <bushman@rsu.ru>
To:        Terry Lambert <tlambert2@mindspring.com>
Cc:        hackers@freebsd.org
Subject:   Re[2]: nscd for freebsd
Message-ID:  <165845726.20030620095811@rsu.ru>
In-Reply-To: <3EF29B78.11DF3FA4@mindspring.com>
References:  <8713472442.20030619163913@rsu.ru> <87k7bi86ve.fsf@PECTOPAH.shenton.org> <3EF29B78.11DF3FA4@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello Terry,

Friday, June 20, 2003, 9:28:24 AM, you wrote:

TL> Chris Shenton wrote:
>> Michael Bushkov <bushman@rsu.ru> writes:
>> > Can anyone tell me if there is an implementation of nscd for FreeBSD?
>> 
>> For DNS information, have a look at "dnscache" from the djbdns suite.
>> Small, secure, fast.
>> 
>> http://cr.yp.to/djbdns.html
>> http://www.lifewithdjbdns.org/
>> 
>> If you're trying to cache other data, sorry to bother you.

TL> We are not trying to cache; if any caching happens, it'll be
TL> a side benefit.  What we are trying to do is come up with a
TL> model that:

TL> 1)      Moves the dynamically loaded NSS modules out of the
TL>         program address space, and onto the other end of a
TL>         communications channel, so that statically linked
TL>         programs can benefit from NSS modules that are not
TL>         statically compiled into them.

TL> 2)      Allow multiple outstanding simultaneous requests on
TL>         the communications channel from a given program, so
TL>         as to provide a cheap and easy way to implement the
TL>         support for the gethostaddr_r() and similar functions,
TL>         which cannot otherwise be easily made thread safe,
TL>         without consuming a socker per thread calling them.

TL> If this yields caching as well, that's just gravy, not the goal.

TL> -- Terry

Ok, so if we do a daemon and call all nss_functions from it - will it
help? We'll solve all the problems with statically/dinmically linked
programs and we'll be able to make some caching, by
the way.

We've done such work. As a start, we have implemented nss_files module, which
worked wit a special NSSD daemon. Libc communicated with them using
sockets. That decision worked quite fast and was very stable. If we
port nss_ldap (by PADL.com) and add some caching procedures, we'll
have almost a lookupd analog.

Michael A. Bushkov
Computer Center of Rostov State University

mailto:bushman@rsu.ru



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?165845726.20030620095811>