From owner-freebsd-hackers@FreeBSD.ORG Mon May 17 16:28:32 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1379316A4CE; Mon, 17 May 2004 16:28:32 -0700 (PDT) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF9B43D39; Mon, 17 May 2004 16:28:31 -0700 (PDT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.12.9p2/8.12.9) with ESMTP id i4HNSS3F035506; Tue, 18 May 2004 03:28:28 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.12.9p2/8.12.9/Submit) id i4HNSRDB035501; Tue, 18 May 2004 03:28:27 +0400 (MSD) (envelope-from yar) Date: Tue, 18 May 2004 03:28:27 +0400 From: Yar Tikhiy To: Cyrille Lefevre Message-ID: <20040517232827.GD27584@comp.chem.msu.su> References: <20040515092114.GB67531@comp.chem.msu.su> <042601c43a6b$cd1cb9a0$7890a8c0@dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <042601c43a6b$cd1cb9a0$7890a8c0@dyndns.org> User-Agent: Mutt/1.5.6i cc: arch@freebsd.org cc: hackers@freebsd.org Subject: Re: Interoperation of flock(2), fcntl(2), and lockf(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 23:28:32 -0000 On Sat, May 15, 2004 at 01:00:13PM +0200, Cyrille Lefevre wrote: > "Yar Tikhiy" wrote: > [snip] > > Considering all the above, I'd like to add the following paragraph > > to the flock(2), lockf(3), and fcntl(2) man pages (replacing the > > sentence quoted from lockf(3)): > > > > The flock(2), fcntl(2), and lockf(3) locks are compatible. > > Processes using different locking interfaces can cooperate > > over the same file safely. However, only one of such > > interfaces should be used within a process. If a file is > > s/a process/the same process/ ? Agreed, thanks! BTW, since no objections were raised and Kirk encouraged me to make the change (thank you Kirk!), I just did so. -- Yar