From owner-freebsd-current@FreeBSD.ORG Thu Apr 1 10:53:32 2004 Return-Path: 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 CFDA716A4CE; Thu, 1 Apr 2004 10:53:32 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06ECE43D1F; Thu, 1 Apr 2004 10:53:32 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.11/8.12.11) with ESMTP id i31IrOhZ076792; Thu, 1 Apr 2004 22:53:24 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.11/8.12.11/Submit) id i31IrO3s076790; Thu, 1 Apr 2004 22:53:24 +0400 (MSD) (envelope-from ache) Date: Thu, 1 Apr 2004 22:53:22 +0400 From: Andrey Chernov To: "Jacques A. Vidrine" , current@FreeBSD.org Message-ID: <20040401185320.GA76718@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , "Jacques A. Vidrine" , current@freebsd.org References: <20040331133132.GA2106@nagual.pp.ru> <20040331183921.GA14949@madman.celabo.org> <20040401160429.GA3346@nagual.pp.ru> <20040401163258.GA63164@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040401163258.GA63164@madman.celabo.org> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.24.0.7; VDF 6.24.0.76 (host: pobrecita.freebsd.ru) Subject: Re: Last NSS commit is very dangerous X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 01 Apr 2004 18:53:32 -0000 On Thu, Apr 01, 2004 at 10:32:58AM -0600, Jacques A. Vidrine wrote: > > But previous NSS variant can handle this unreadable > > /etc/nsswitch.conf nicely, probably using defaults. > > I believe you are mistaken. Are you 100% certain that revision 1.10 of > nsdispatch.c falls back to defaults if /etc/nsswitch.conf exists but is In new version you add + result = errno; if file can't be opened. I think this makes difference. > ``unreadable /etc/nsswitch.conf'' is a different situation than ``no > /etc/nsswitch.conf''. The latter means ``gimme the defaults''. The > former means ``disable NSS''. You are probably right, I have no strong preferences here. It depends on other system's historic nsswitch.conf behaviour and it will be better, if unreadable case will be documented in nsswitch.conf(5). Currently we have: "If, for any reason, nsswitch.conf doesn't exist, or it has missing or corrupt entries, nsdispatch(3) will default to an entry of ``files'' for the requested database." Which not covers "unreadable" case. -- Andrey Chernov | http://ache.pp.ru/