From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 19 22:29:48 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 BB68C37B401 for ; Thu, 19 Jun 2003 22:29:48 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D98C43F85 for ; Thu, 19 Jun 2003 22:29:48 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-uinj93o.dialup.mindspring.com ([165.121.164.120] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19TESp-0001Ry-00; Thu, 19 Jun 2003 22:29:31 -0700 Message-ID: <3EF29B78.11DF3FA4@mindspring.com> Date: Thu, 19 Jun 2003 22:28:24 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Chris Shenton References: <8713472442.20030619163913@rsu.ru> <87k7bi86ve.fsf@PECTOPAH.shenton.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4dc282962027a7df9fe81aedaeb138aa0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: hackers@freebsd.org cc: Michael Bushkov Subject: Re: nscd for freebsd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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:29:49 -0000 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. We are not trying to cache; if any caching happens, it'll be a side benefit. What we are trying to do is come up with a model that: 1) Moves the dynamically loaded NSS modules out of the program address space, and onto the other end of a communications channel, so that statically linked programs can benefit from NSS modules that are not statically compiled into them. 2) Allow multiple outstanding simultaneous requests on the communications channel from a given program, so as to provide a cheap and easy way to implement the support for the gethostaddr_r() and similar functions, which cannot otherwise be easily made thread safe, without consuming a socker per thread calling them. If this yields caching as well, that's just gravy, not the goal. -- Terry