From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 07:48:48 2003 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 A133337B401 for ; Mon, 28 Apr 2003 07:48:48 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id D507943F85 for ; Mon, 28 Apr 2003 07:48:47 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 522724; Mon, 28 Apr 2003 09:48:47 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id A4DC578C66; Mon, 28 Apr 2003 09:48:46 -0500 (CDT) Date: Mon, 28 Apr 2003 09:48:46 -0500 From: "Jacques A. Vidrine" To: Lowell Gilbert Message-ID: <20030428144846.GA29465@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Lowell Gilbert , freebsd-current@freebsd.org References: <20030428075916.GA53857@myhakas.internal> <20030428190209.A21656@dilbert.robbins.dropbear.id.au> <20030428075916.GA53857@myhakas.internal> <20030428080505.GA1474@chihiro.leafy.idv.tw> <20030428075916.GA53857@myhakas.internal> <20030428105521.GB2676@madman.celabo.org> <20030428111859.GA2923@madman.celabo.org> <44n0iallyq.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44n0iallyq.fsf@be-well.ilk.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: freebsd-current@freebsd.org Subject: Re: Somethings still up with new NSS? 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: Mon, 28 Apr 2003 14:48:49 -0000 On Mon, Apr 28, 2003 at 10:45:33AM -0400, Lowell Gilbert wrote: > "Jacques A. Vidrine" writes: > > > So until I add logic to pwd_mkdb(8) to recognize and deal > > appropriately with this situation, it is best to run pwd_mkdb once > > manually after the NSS commit. > > Wouldn't an easy solution be to put a comment into master.passwd > itself? It can serve as a warning, and it will change the CVS tag > (thus, mergemaster will offer to rebuild the database after a proper > merge). I don't think this would give very good coverage ... usually one does not merge master.passwd. Clever thought, nonetheless. Anyway, I've already committed a workaround to pwd_mkdb. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se