From owner-freebsd-hackers Fri May 3 5:29:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from sea-incorporated.com (caribbean.sea-incorporated.com [209.74.10.130]) by hub.freebsd.org (Postfix) with ESMTP id C5B2937B41B for ; Fri, 3 May 2002 05:29:35 -0700 (PDT) Received: from localhost (geoff@localhost) by sea-incorporated.com (8.9.3/8.9.3) with ESMTP id IAA15722; Fri, 3 May 2002 08:29:30 -0400 (EDT) (envelope-from geoff@sea-incorporated.com) Date: Fri, 3 May 2002 08:29:30 -0400 (EDT) From: "Geoffrey C. Speicher" To: "Matthew D. Fuller" Cc: Matt Simerson , freebsd-hackers@freebsd.org Subject: Re: bug in pw, freebsd 4.5 In-Reply-To: <20020502173110.B22449@over-yonder.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 May 2002, Matthew D. Fuller wrote: > Well, the stab didn't go because nobody was interested 8-) Sorry --- I was interested, but I didn't see your original message. This problem has been biting me (and a client) in the ass for quite some time. > I actually had in mind some farther-reaching changes, which would (after > 'fixing' pw) include potentially rewriting adduser(8) and friends to > backend into pw to; sort of consolidate the user-management stuff a bit. While I was looking through the sources yesterday, I was wondering why so many pieces were reimplemented time and again. So I'd say that sounds like a worthwhile cause. > What do people think of using the external lock file (well, I can't > actually think of any OTHER way to do it, so...)? I'm thinking /var/run, > but on the flipside just putting it in /etc might be cleaner. Comments? Hmm. hier(7) describes /var/run thusly: run/ system information files describing various info about system since it was booted I guess it could be easily argued that "the password file is currently locked" describes information about the system since it was booted. :) Geoff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message