Date: Mon, 28 Apr 2003 09:48:46 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Lowell Gilbert <freebsd-current-local@be-well.no-ip.com> Cc: freebsd-current@freebsd.org Subject: Re: Somethings still up with new NSS? Message-ID: <20030428144846.GA29465@madman.celabo.org> In-Reply-To: <44n0iallyq.fsf@be-well.ilk.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 28, 2003 at 10:45:33AM -0400, Lowell Gilbert wrote: > "Jacques A. Vidrine" <nectar@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030428144846.GA29465>