From owner-freebsd-current@FreeBSD.ORG Mon Nov 13 13:04:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90CCE16A47C; Mon, 13 Nov 2006 13:04:43 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0347243D69; Mon, 13 Nov 2006 13:04:42 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id kADD4f38028949; Mon, 13 Nov 2006 08:04:41 -0500 (EST) Date: Mon, 13 Nov 2006 08:04:41 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Michael Bushkov In-Reply-To: <200611131537.12954.bushman@freebsd.org> Message-ID: References: <20061113115839.GL59604@dimma.mow.oilspace.com> <200611131537.12954.bushman@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-2.0.2 (mail.ntplx.net [204.213.176.10]); Mon, 13 Nov 2006 08:04:41 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-current@freebsd.org, Dmitriy Kirhlarov Subject: Re: nscd for freebsd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 13:04:43 -0000 On Mon, 13 Nov 2006, 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. If it now performs the same thing as Linux/Solaris nscd, then can we change the name to nscd and nscd.conf before 7.0 goes out the door? -- DE