fcntl (locking) bug?

[Corinna Vinschen]

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/