X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=apQfWYjW6bPchC/1
	6Jw4bxg88SeRA0bplEUs6c+e2Um6g0k3UK4oCAOO67VYDrzDtJA+3eivU8rShy1t
	f5REbx2kGwFFSnSt4PTlL2G3qmEmgjsGfELG5okUlfjZPz4ER/pjPEK7omsfxhEJ
	F+5zaETRGNreXDuuYnk32u4dSTA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=uL7N/UNZUxZqDJzmS8z9Hj
	9PzNM=; b=Jwani2ZvonKu4PIKw7Hcrc3H1hcnXxg8fZOu9H44maoApVd95fwTWF
	FjmbXiufkjOVSdn4dbhbI43KDxI9RrZqNCN41w4Ej7sXt0x1KeZpfapITOXo7FUa
	/sDXdP9XWgzXdpu9T4XTZ/FWSxPPuqe+T6oO7mcMSV7LEZcF5+zYk=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtp.ht-systems.ru
Date:	Tue, 2 Dec 2014 09:12:04 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<383215052.20141202091204@yandex.ru>
To:	"Kyle R." <kroes921 AT gmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Fatal error using flock
In-Reply-To:	<CAFSgOmZQ2WCABJa0gdN_7A2PhE+8CguqjA7ZQ8xXcDdc7OnDWw@mail.gmail.com>
References:	<CAFSgOmZQ2WCABJa0gdN_7A2PhE+8CguqjA7ZQ8xXcDdc7OnDWw AT mail DOT gmail DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

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 AT yandex DOT 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

- Raw text -