X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sun, 7 Jun 2009 21:34:52 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: fcntl (locking) bug? Message-ID: <20090607193452.GI25832@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1MDHlF-1c6ct60@fwd01.t-online.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1MDHlF-1c6ct60@fwd01.t-online.de> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Jun 7 14:45, Margit Schubert-While wrote: > 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. For people used to the Win32 API, it is ;) > 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 ? Doesn't matter anyway. We're heading straight to the 1.7 release anyway. It would make more sense if you could give the fcntl locking mechanism in Cygwin 1.7 a try. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/