From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 19:45:09 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org 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 DE9B916A422; Tue, 6 Dec 2005 19:45:08 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE88D43D69; Tue, 6 Dec 2005 19:44:57 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from jersey (p49.mp96.aaanet.ru [80.80.96.49]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jB6Ji2wo078126 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 6 Dec 2005 22:44:11 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <000c01c5fa9d$7d219710$0100a8c0@jersey> From: "Michael Bushkov" To: "Julian Elischer" References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> Date: Tue, 6 Dec 2005 22:44:02 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:45:09 -0000 I haven't seen much fuss, actually :) Here are some points: 1. Nsswitch makes caching easy. As nsswitch-related calls are done quite often, caching can be very useful. With nsswitch we can organize caching of different types of data (passwd, groups, services, etc) in the quite simple uniform manner. In other OSes caching is usually organized via nscd. The caching daemon (it's implementation is in the patch) is the analogue of the nscd in some way. It has different approach for caching, but can work in the way, the nscd usually works. 2. Nsswitch implementation is not yet completed. There's a number of databases, which can be supported, but their support is not yet implemented. Their support in nsswitch will give us: a) uniform way to configure the data sources to use (via nsswitch.conf) 2) the ability to cache their data 3. More concrete example is /etc/services file. The services database didn't utilize nsswitch/nsdispatch. If it uses nsdispatch, it will be able to cache data from the file - and we'll be able to make it as big as we want. Of course, first "uncached" requests will take some time, but all subsequent requests for the information, that is already in the cache will be extremely fast - they won't event open the /etc/services file. 4. Another concrete example is OpenSSH authroization keys. If we use nsswitch to retrieve them, we can easily use NIS or LDAP as their storage, which is a good thing. I hope, this will satisfy you :) With best regards, Michael ----- Original Message ----- From: "Julian Elischer" To: "Michael Bushkov" Cc: ; Sent: Tuesday, December 06, 2005 9:46 PM Subject: Re: [PATCH] nsswitch extensions + caching > Michael Bushkov wrote: > [...] > > so, I've been wonderring.. what's all the fuss about nsswitch? > what does it get us? > (Not saying it doesn't, just hoping someone will explain) >