X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Date: Sun, 07 Jun 2009 14:45:54 +0200
To: cygwin AT cygwin DOT com
From: Margit Schubert-While <margitsw AT t-online DOT de>
Subject: fcntl (locking) bug?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <1MDHlF-1c6ct60@fwd01.t-online.de>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


 >> This is 1.5.25 but also happens on earlier versions.
 >> It would appear that placing a shared read lock
 >> on a file open for input/output is preventing the
 >> the process itself from writing.

Corinna scribeth :
 > Cygwin up to release 1.5.25 implements fcntl locks using Windows file
 > locking calls.  Windows semantics disallow write access to a shared lock
 > for all processes, even the one setting up the first lock.  Only an
 > exclusive lock allows the locking process to write.

Hmm. Unfortunate and not intuitive. Hmm - fcntl is in the
Cygwin SUSV3 compat list 
-http://cygwin.com/cygwin-api/compatibility.html#std-susv3  ?
SUSV3 mandates this functionality.
Maybe an addendum somewhere or an entry
in http://cygwin.com/cygwin-api/std-notes.html ?

Margit 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/