From owner-freebsd-bugs Wed Mar 13 2:54:53 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id BB6BB37B404; Wed, 13 Mar 2002 02:54:50 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020313105450.PVJU2951.rwcrmhc53.attbi.com@blossom.cjclark.org>; Wed, 13 Mar 2002 10:54:50 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g2DAsnk36499; Wed, 13 Mar 2002 02:54:49 -0800 (PST) (envelope-from cjc) Date: Wed, 13 Mar 2002 02:54:49 -0800 From: "Crist J. Clark" To: billf@FreeBSD.ORG Cc: irys@irc.pl, freebsd-bugs@FreeBSD.ORG Subject: Re: i386/35816: no one can change password, because "passwd DB is locked" Message-ID: <20020313025449.R29705@blossom.cjclark.org> References: <200203121143.g2CBhqd03584@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200203121143.g2CBhqd03584@freefall.freebsd.org>; from billf@FreeBSD.ORG on Tue, Mar 12, 2002 at 03:43:52AM -0800 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Mar 12, 2002 at 03:43:52AM -0800, billf@FreeBSD.ORG wrote: > Synopsis: no one can change password, because "passwd DB is locked" > > State-Changed-From-To: open->closed > State-Changed-By: billf > State-Changed-When: Tue Mar 12 03:41:48 PST 2002 > State-Changed-Why: > this is not a bug. root can find the process that is holding the lock > on the password database and kill both it and the user holding it. This does look like a bug to me. I don't understand why chpass(1) needs to hold a lock on the database while the user is editing his entry. It seems like once the user is done editing, _then_ the master.passwd can be locked, the user's modifications checked, and then added if they are OK. Why would it need to be locked during the editing process? I don't see a good reason looking at the code. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message