From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 19 22:58:24 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 172F237B401 for ; Thu, 19 Jun 2003 22:58:24 -0700 (PDT) Received: from smtp.aaanet.ru (smtp.aaanet.ru [80.80.111.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A8B343F75 for ; Thu, 19 Jun 2003 22:58:23 -0700 (PDT) (envelope-from bushman@rsu.ru) Received: from [80.80.119.234] (helo=p75) by smtp.aaanet.ru with esmtp (Exim 4.14) id 19TEub-0006BB-Rs; Fri, 20 Jun 2003 09:58:16 +0400 Date: Fri, 20 Jun 2003 09:58:11 +0400 From: Michael Bushkov X-Mailer: The Bat! (v1.62i) Organization: RSU X-Priority: 3 (Normal) Message-ID: <165845726.20030620095811@rsu.ru> To: Terry Lambert In-Reply-To: <3EF29B78.11DF3FA4@mindspring.com> References: <8713472442.20030619163913@rsu.ru> <87k7bi86ve.fsf@PECTOPAH.shenton.org> <3EF29B78.11DF3FA4@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re[2]: nscd for freebsd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Michael Bushkov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2003 05:58:24 -0000 Hello Terry, Friday, June 20, 2003, 9:28:24 AM, you wrote: TL> Chris Shenton wrote: >> Michael Bushkov 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