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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=R6gj7uh9fugiKixnyxR8HZxszD1Mo917AjgVO4OOsPRHf4r6eBq+2
	K0yZr/G4PcEWnn0idQwv8IIJFUipypyzb5p6oP3xF0gYuwf+tWMHgvkV8i1jUJX/
	cDKw05ikxWE2O5fynd+T6Q51TSQXIK8Lc3Gjccju3JXjoOeVKF4jZw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 4 Dec 2014 10:33:52 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Fatal error using flock
Message-ID: <20141204093352.GB3810@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <547fa827 DOT 02996b0a DOT 02fc DOT ffffaf7b AT mx DOT google DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="YZ2gLtJL3Gv805BH"
Content-Disposition: inline
In-Reply-To: <547fa827.02996b0a.02fc.ffffaf7b@mx.google.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--YZ2gLtJL3Gv805BH
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec  3 18:25, Kyle R. wrote:
> On Dec  2 16:52, Corinna Vinshen wrote:
                           ^^^^^^^
                           oops
> > 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.
> >=20
> > I applied a patch and created a new developer snapshot on
> > https://cygwin.com/snapshots/
> >=20
> > Please give it a try.
>=20
> Thanks Corinna, that works perfectly!

Thanks for testing.  And thanks again for providing an STC, that's
very helpful.

> On Dec  2 14:48, Corrina Vinshen wrote:
                   ^^^^^^^^^^^^^^^
                   it's getting worse :)
> > Pity.  When I created the locking code I added lots and lots of comments
> > in the hope that
> >=20
> >   a) other people would have a chance to understand how the code is
> >      supposed to work and
> >=20
> >   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...
>=20
> 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=20
> 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. :)

Sure, I'd be glad!  Only... it's mostly Win32/NT, not Linux code at this
eoint in the source ;)


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--YZ2gLtJL3Gv805BH
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUgCqAAAoJEPU2Bp2uRE+g7XgP/3zwzyWShOGd0H/pEpL1y3et
GQwEqXphzdOS68Lcjwj1zInblotgUDcVDoz3H0c8eMpKMH//BJnGaGWndoZa+XHS
FwrLEIqpKcFz1zES79Md241tgEKrxzZmk/ULQRFKILPYYYgatm4oAq/KGtGN3Bdn
L1DFVjyOey3LN6ruu4RUSe0T1IBfMc90QHI0ozR369EpGyAPIDhPiBvGXjYdbgW+
qA1navA4Q+8rUUzbcJ/309RMNuZHpEI0Nly1363AuNcHKHzKLV+qjr7L1auIorr2
Lj4vTtx/JOw0C621+OC0vStRXoUr/UQUd6gFuhKy3v4P91lPdDvuGaoiGeiqSMGf
2dSCgZhIqLLE8Zxri8cumg+B2ENGJK9pqKQP+jyAEy+pFzmCsgUBCxFccJCgZNCf
55OKPKNqkTWyeEJQEVjv68bs1JDcfxeLK/G5J1hHwtO4G5mu4Lz6MsSHepIhKRmJ
p03L5waRtBmAx+sDeqosb8YHf2vOH0b31DHmMiWa5B3Jsv+1jcApAt3FYpkMm/9/
RMJMt80FjoOMqLixQpIfVYUoRvAcx3M9v8AOPfmdXx6KrtAoUsn6nTgZqGYfkZkU
ELzUz6k1OjtQNEcHHbhYks5knLcaE68OlEF/WD9nCZ0cZn8rRhMVF5cYvPfxNgti
W2PyM3c05TxYyzuJd2rw
=jthY
-----END PGP SIGNATURE-----

--YZ2gLtJL3Gv805BH--