From owner-freebsd-current  Fri Jul 31 20:41:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA23616
          for freebsd-current-outgoing; Fri, 31 Jul 1998 20:41:52 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23611
          for <freebsd-current@FreeBSD.ORG>; Fri, 31 Jul 1998 20:41:51 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA26788;
	Fri, 31 Jul 1998 20:39:16 -0700 (PDT)
Message-Id: <199808010339.UAA26788@implode.root.com>
To: Terry Lambert <tlambert@primenet.com>
cc: green@zone.baldcom.net (Brian Feldman), mike@smith.net.au,
        freebsd-current@FreeBSD.ORG
Subject: Re: flock(2) problem & fix 
In-reply-to: Your message of "Sat, 01 Aug 1998 03:02:55 -0000."
             <199808010302.UAA06065@usr06.primenet.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 31 Jul 1998 20:39:15 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>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.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message