From owner-freebsd-stable Sun Jun 23 5:59:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hardtime.linuxman.net (hardtime.linuxman.net [66.147.26.65]) by hub.freebsd.org (Postfix) with ESMTP id 7E7C837B401 for ; Sun, 23 Jun 2002 05:59:39 -0700 (PDT) Received: from mortis.over-yonder.net (localhost [127.0.0.1]) by hardtime.linuxman.net (8.11.6/8.11.6) with ESMTP id g5NC4rB27011; Sun, 23 Jun 2002 07:04:53 -0500 Received: by mortis.over-yonder.net (Postfix, from userid 100) id 6F7591F02; Sun, 23 Jun 2002 07:59:34 -0500 (CDT) Date: Sun, 23 Jun 2002 07:59:34 -0500 From: "Matthew D. Fuller" To: "Geoffrey C. Speicher" Cc: Paul Herman , freebsd-stable@FreeBSD.ORG, Matt Simerson Subject: Re: bug in pw, -STABLE [patch] Message-ID: <20020623125934.GB81018@over-yonder.net> References: <20020623000216.E37393-100000@mammoth.eat.frenchfries.net> <20020623083510.K29729-100000@sea-incorporated.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020623083510.K29729-100000@sea-incorporated.com> User-Agent: Mutt/1.4i-fullermd.1 X-Editor: vi X-OS: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 23, 2002 at 08:45:58AM -0400 I heard the voice of Geoffrey C. Speicher, and lo! it spake thus: > > You raise a good point about concurrent pw(8)s with different -V > parameters, and I would think that the solution would be either to use a > different pid file for each -V, or to not worry about it for pw(8) and > have concurrent instances sometimes block briefly when it's not necessary. I've thought about this a bit. My gut reaction is lean toward "Oh well, it'll block sometimes", since I would tend to consider the cases where you have contention reasonablly rare in practice, and cases where you'd get a 'pileup' that lasts longer than 2 or 3 processes practically nonexistent. On the other hand, I'm not against adding a command-line option and/or a pw.conf option (since a different pw.conf file will be loaded with each -V) to pw(8) to specify the lock file location. I'm currently polishing up the edges of the pid_*() functions; expect a patch relating to that shortly. If we can get those 'frozen', as it were, then I can revisit my pw_auth*() functions and see what among them will be necessary to keep, to push the use of the file out to pw(8) and passwd(1) and chpass(1) and pwd_mkdb(8) and vipw(8) and all that jazz. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message