On Jun 7 11:15, Margit Schubert-While wrote: > 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.
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. This is supposed to be fixed in Cygwin 1.7 which will use an entire different mechanism to implement POSIX locks. 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/
