Date: Sun, 10 Jan 1999 21:43:51 +0100 From: Jos Backus <Jos.Backus@nl.origin-it.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Two seem-to-be bugs with 3.0-SNAP Message-ID: <19990110214351.A13555@hal.mpn.cp.philips.com> In-Reply-To: <199901101747.JAA86041@apollo.backplane.com>; from Matthew Dillon on Sun, Jan 10, 1999 at 09:47:27AM -0800 References: <199901101747.JAA86041@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 10, 1999 at 09:47:27AM -0800, Matthew Dillon wrote:
> Ah, I missed that one. pwd_mkdb was earlier modified to do locking
> (which it didn't do before). So now that it does, programs that
> use it shoulds either use pwd_mkdb's -N option so they can hold their
> own lock all the way through, or not hold a lock.
I guess pw shouldn't lock /etc/master.passwd in this case (davidn removed it),
because I recall changing the call inside pw to pwd_mkdb, adding the -N flag,
but that wouldn't work either because the pwdb call in pwupd.c(pw_update)
would return with an error in that case (because of the LOCK_EX failing).
But my memory is starting to get hazy on the subject.
Cheers,
--
Jos Backus _/ _/_/_/ "Reliability means never
_/ _/ _/ having to say you're sorry."
_/ _/_/_/ -- D. J. Bernstein
_/ _/ _/ _/
Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer;
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990110214351.A13555>