From owner-freebsd-current@FreeBSD.ORG  Mon Apr 28 07:45:40 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 2230F37B40E; Mon, 28 Apr 2003 07:45:40 -0700 (PDT)
Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DE3DF43FB1; Mon, 28 Apr 2003 07:45:38 -0700 (PDT)
	(envelope-from freebsd-current-local@be-well.no-ip.com)
Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com[24.147.188.198])
          by rwcrmhc52.attbi.com (rwcrmhc52) with ESMTP
          id <2003042814453805200nr2upe>; Mon, 28 Apr 2003 14:45:38 +0000
Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198]
	(may be forged))
	by be-well.ilk.org (8.12.9/8.12.7) with ESMTP id h3SEjbPN098291;
	Mon, 28 Apr 2003 10:45:37 -0400 (EDT)
	(envelope-from freebsd-current-local@be-well.no-ip.com)
Received: (from lowell@localhost)
	by be-well.ilk.org (8.12.9/8.12.6/Submit) id h3SEjXFn098288;
	Mon, 28 Apr 2003 10:45:33 -0400 (EDT)
X-Authentication-Warning: be-well.ilk.org: lowell set sender to
	freebsd-current-local@be-well.ilk.org using -f
Sender: lowell@be-well.no-ip.com
To: "Jacques A. Vidrine" <nectar@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>
From: Lowell Gilbert <freebsd-current-local@be-well.no-ip.com>
Date: 28 Apr 2003 10:45:33 -0400
In-Reply-To: <20030428111859.GA2923@madman.celabo.org>
Message-ID: <44n0iallyq.fsf@be-well.ilk.org>
Lines: 10
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2003 14:45:40 -0000

"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).