Date: Sat, 01 Aug 1998 08:18:54 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: dg@root.com Cc: Terry Lambert <tlambert@primenet.com>, green@zone.baldcom.net (Brian Feldman), mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: flock(2) problem & fix Message-ID: <2244.901952334@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 31 Jul 1998 20:39:15 PDT." <199808010339.UAA26788@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199808010339.UAA26788@implode.root.com>, David Greenman writes: >>Anyway, suffice to say, I think exclusive locking a file without the >>intention *or possibility* of writing is an "ok thing to do". > > For what it's worth, I agree. I also asked Kirk McKusick, the author of >the advisory locking code, and he thinks similarly. I agree, it means "I need a consistent view of this file, don't mess with it." Which is a legitimate thing to ask for. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal 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?2244.901952334>