This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Fatal error using flock
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: "Kyle R." <kroes921 at gmail dot com>, cygwin at cygwin dot com
- Date: Tue, 2 Dec 2014 09:12:04 +0300
- Subject: Re: Fatal error using flock
- Authentication-results: sourceware.org; auth=none
- References: <CAFSgOmZQ2WCABJa0gdN_7A2PhE+8CguqjA7ZQ8xXcDdc7OnDWw at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot com
Greetings, Kyle R.!
> I've run into a problem with flock while doing some parallel scripting
> in bash (also seen in dash) on the latest 64-bit version of Cygwin
> running on Windows 8.1. In the attached simple test case, the code
> locks and unlocks a file in a loop. After the first iteration of the
> loop is completed, this error is thrown:
> 0 [main] flock 7008 C:\cygwin64\bin\flock.exe: *** fatal error -
> NtCreateEvent(lock): 0xC0000035
> ./test.sh: line 12: 7008 Hangup flock -x 5
I can confirm this for Win7/64 and 64-bit Cygwin on both .34 exp and snapshot
versions of Cygwin library.
> However, the problem doesn't occur if I comment out the "while true
> do" and "done" and call the script file from a while loop in another
> bash script. I found a similar problem in an older thread (here:
> https://sourceware.org/ml/cygwin/2011-08/msg00480.html) which may help
> to shed some light on the issue, but the inner workings of the locking
> system is a bit beyond me. My full Cygwin version is "CYGWIN_NT-6.3
> 1.7.33-2(0.280/5/3) 2014-11-13 15:47", and my cygcheck output is
> attached along with the STC and flock's stackdump. The cygcheck output
> has been edited to remove one license server address.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 02.12.2014, <09:10>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple