From owner-freebsd-current@FreeBSD.ORG Thu Apr 1 11:15:09 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 A454D16A4CE for ; Thu, 1 Apr 2004 11:15:09 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C64843D41 for ; Thu, 1 Apr 2004 11:15:09 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (not verified)) by gw.celabo.org (Postfix) with ESMTP id E296354861; Thu, 1 Apr 2004 13:15:08 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id 8ACC76D465; Thu, 1 Apr 2004 13:15:08 -0600 (CST) Date: Thu, 1 Apr 2004 13:15:08 -0600 From: "Jacques A. Vidrine" To: Andrey Chernov , current@freebsd.org Message-ID: <20040401191508.GA4871@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Andrey Chernov , current@freebsd.org References: <20040331133132.GA2106@nagual.pp.ru> <20040331183921.GA14949@madman.celabo.org> <20040401160429.GA3346@nagual.pp.ru> <20040401163258.GA63164@madman.celabo.org> <20040401185320.GA76718@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040401185320.GA76718@nagual.pp.ru> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.6i 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 19:15:09 -0000 On Thu, Apr 01, 2004 at 10:53:22PM +0400, Andrey Chernov wrote: > 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. Andrey, I must apologize. I just couldn't see this line for some reason :-/ Thanks for your patience in getting me to see the problem. > > ``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. I think the behavior must be the same as it was previously. I believe I have fixed the problem in rev 1.12 of nsdispatch.c by removing the offending statement. In short, you are right, I am wrong, sorry for the noise :-) Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org