Date: Mon, 28 Apr 2003 21:09:01 +0300 From: Vallo Kallaste <kalts@estpak.ee> To: "Jacques A. Vidrine" <nectar@FreeBSD.org>, Lowell Gilbert <freebsd-current-local@be-well.no-ip.com>, freebsd-current@FreeBSD.org Subject: Re: Somethings still up with new NSS? Message-ID: <20030428180901.GA1009@kevad.internal> In-Reply-To: <20030428144846.GA29465@madman.celabo.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> <20030428144846.GA29465@madman.celabo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 28, 2003 at 09:48:46AM -0500, "Jacques A. Vidrine" <nectar@FreeBSD.org> wrote: > > > 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. I'm beating the dead horse now, but what has happened to idea of tracking such events in the UPDATING file? I did remember the NSS update when I updated my system and specifically looked into UPDATING to get some clues beforehand, but found nothing. This has two sides, of course, it had probably saved my ass but the bug remained. -- Vallo Kallaste
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030428180901.GA1009>