From owner-freebsd-current@FreeBSD.ORG Fri Jun 8 13:32:28 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 20FCC16A468 for ; Fri, 8 Jun 2007 13:32:28 +0000 (UTC) (envelope-from dimma@higis.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id B980A13C48C for ; Fri, 8 Jun 2007 13:32:27 +0000 (UTC) (envelope-from dimma@higis.ru) Received: from msk-ly-gw1.masterhost.ru ([87.242.97.36]:63228 helo=dimma.masterhost.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1HweZe-000DR8-Sm for current@freebsd.org; Fri, 08 Jun 2007 13:32:18 +0000 Message-ID: <46695A61.9000604@higis.ru> Date: Fri, 08 Jun 2007 17:32:17 +0400 From: Dmitriy Kirhlarov User-Agent: Thunderbird 2.0.0.0 (X11/20070603) MIME-Version: 1.0 To: current@freebsd.org References: <20061113115839.GL59604@dimma.mow.oilspace.com> <200611131537.12954.bushman@freebsd.org> In-Reply-To: <200611131537.12954.bushman@freebsd.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: nscd for freebsd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2007 13:32:28 -0000 Hi, list Some time ago we are discuss about renaming 'cached' to 'nscd': http://docs.freebsd.org/cgi/getmsg.cgi?fetch=338214+0+archive/2006/freebsd-current/20061119.freebsd-current Could somebody talk me current situation with this (especially I'm interesting plans for MFC). Michael Bushkov wrote: > On Monday 13 November 2006 14:58, Dmitriy Kirhlarov wrote: >> I'm interested in name service caching daemon for freebsd (it's useful >> for external userbase, stored in ldap and for monitoring hosts, with >> resolving/polling of many hosts). It's much more useful, then local >> cached named and local ldap replica. >> >> I found "cached" daemon in HEAD. >> >> Can somebody answer me -- when this daemon will be MFC-ed to RELENG_6? >> Also why this strange name? >> It's impossible to find this name in google, cause this daemon used to >> be called nscd. >> Is there any reason for inventing new name? >> > Actually, cached is called "cached" because initially it was intended only to > cache the already obtained results of nsswitch queries. This is not how nscd > behaves. Nscd makes all queries (to LDAP, NIS, etc) by itself and caches the > results. cached only cached the results of requests, that have been actually > made by other applications. The name "cached" was used to highlight this > difference. > > Later, however, the nscd-like functionality was added to cached, but the name > was left unchanged. Personally I don't see any reasons why "cached" can't be > renamed to nscd right now - so I guess, it would happen in the nearest > future. > > cached is similar to nscd in many ways (including configuration file). To > enable nscd-like behavior for particular nsswitch database (so that cached > will make all queries by itself), "perform-actual-lookups" directive should > be specified in cached.conf. Please see cached(8) manual page for more > details about this. The choice of using or not using "perform-actual-lookups" > mode depends on many factors and should be made by system administrator. The > default value for this option is "no". > > Can't say anything about when cached would be MFC'ed. All I can say is that > it's possible. It will require a number of changes in libc, but they all are > fine-grained and, as far as I remember, the patch, that I've used to add > caching support to -CURRENT was almost clearly applicable to RELENG_6. > WBR. Dmitriy