On Apr 20 17:45, Eric Blake wrote:
> I did notice that flock only seems to protect processes spawned in the
> same cygwin process hierarchy - using strace to spawn my test program
> created a new hierarchy, and thus did not see the lock held by the old
> hierarchy. That does not affect the origina
Corinna Vinschen cygwin.com> writes:
> Because this testcase works fine. I hope it's not trying to do this:
>
> parent opens file
> fork
> child calls flock()
> exit
> fork
> second child relies on the lock.
>
> because this is exactly the scenario which doesn't work with flo
On Apr 20 17:34, Corinna Vinschen wrote:
> On Apr 20 15:14, Eric Blake wrote:
> > Corinna Vinschen cygwin.com> writes:
> >
> > > > > I'd prefer a testcase in C.
> > > >
> > > > So would I. I'm not even sure whether perl was using flock or
> > > > lockf/fcntl. Do you still need me to try and wr
On Apr 20 15:14, Eric Blake wrote:
> Corinna Vinschen cygwin.com> writes:
>
> > > > I'd prefer a testcase in C.
> > >
> > > So would I. I'm not even sure whether perl was using flock or
> > > lockf/fcntl. Do you still need me to try and write a STC, or at least
> > > test how perl behaves with
Corinna Vinschen cygwin.com> writes:
> > > I'd prefer a testcase in C.
> >
> > So would I. I'm not even sure whether perl was using flock or
> > lockf/fcntl. Do you still need me to try and write a STC, or at least
> > test how perl behaves with your first patch?
>
> I checked in a patch whic
On Apr 17 06:58, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Corinna Vinschen on 4/17/2009 4:01 AM:
> > Default question: Do you have a simple testcase to reproduce this
> > problem? I'm going to play with the lock.pl perl script from
> > http://lists.gnu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 4/17/2009 4:01 AM:
> Default question: Do you have a simple testcase to reproduce this
> problem? I'm going to play with the lock.pl perl script from
> http://lists.gnu.org/archive/html/bug-automake/2009-04/msg00053.h
On Apr 17 12:01, Corinna Vinschen wrote:
> On Apr 16 20:39, Eric Blake wrote:
> > This change in cygwin 1.7:
> >
> > - File locking is now advisory, not mandatory anymore. The fcntl(2) and
> > the new lockf(2) APIs create and maintain locks with POSIX semantics,
> > the flock(2) API creates a
On Apr 16 20:39, Eric Blake wrote:
> This change in cygwin 1.7:
>
> - File locking is now advisory, not mandatory anymore. The fcntl(2) and
> the new lockf(2) APIs create and maintain locks with POSIX semantics,
> the flock(2) API creates and maintains locks with BSD semantics.
> POSIX and
9 matches
Mail list logo