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:message-id:date:to:from:in-reply-to:references :subject; q=dns; s=default; b=Wp77giZJ3SjZ1hSJ2uoPmlkQss6oiaCUUx xjwPxmSAnT65jHnv1Uqku92Q9fv4X9SrUFYzvIvAAzYcSfkgKIChCI+wJmsJR5JN eT17kWHVSMIuhk+Zzuk1brfRxBad+QakBDZFAT1p3fItJXzNK/IEPGtXoJxHWh6s JPdk4LpY8= 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:message-id:date:to:from:in-reply-to:references :subject; s=default; bh=2u4OK9xGzaOcCVuK3nB+gk86zAI=; b=YtNpp85q fRkcmY1DIMxqX8x7lV10MWDd14o7VzJlHDA9TZdjwyj6zfDvfu74ZsTdr5uKV6yE AOhdo7tU+cwXnpVOF7bU7gItiwmQORssWbp/v0laLEu4ELPJe7r+SoumD5WOTzEd q6ck3onXLC5GXAHFlMWZPCtAMpefx3PBqsY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-2.3 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,MSGID_FROM_MTA_HEADER,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ie0-f182.google.com X-Received: by 10.107.156.211 with SMTP id f202mr7364261ioe.15.1417652263643; Wed, 03 Dec 2014 16:17:43 -0800 (PST) Message-ID: <547fa827.02996b0a.02fc.ffffaf7b@mx.google.com> Date: Wed, 03 Dec 2014 18:25:56 -0600 To: cygwin AT cygwin DOT com From: "Kyle R." In-Reply-To: <20141202155213.GX3810@calimero.vinschen.de References: <20141202155213 DOT GX3810 AT calimero DOT vinschen DOT de Subject: Re: Fatal error using flock On Dec 2 16:52, Corinna Vinshen wrote: > Ouch. The handle in the parent got created non-inheritable. That's > bad if the handle is utilized in subsequent child processes which rely > on being able to access the handle. > > I applied a patch and created a new developer snapshot on > https://cygwin.com/snapshots/ > > Please give it a try. Thanks Corinna, that works perfectly! On Dec 2 14:48, Corrina Vinshen wrote: > Pity. When I created the locking code I added lots and lots of comments > in the hope that > > a) other people would have a chance to understand how the code is > supposed to work and > > b) *I* have a chance to understand how the code is supposed to work > after not looking at the code for a year or longer... I should mention that I'm only a grad student with more of a focus in hardware and computer architecture than softare, so I don't have much experience in Linux land yet. Give me a year or so on the job and I may be able to understand and debug this kind of code. :) Thanks again, Kyle R. -- 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