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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=sSCatRt+I+/FHnw1p2joU1YP/j5XlW445Cc5B7IQxS3M27FuTBOO2
	63eDct5+QziUy+T2znv0vjgcE0fOjlSJx+egCjBXVEVzrgdbzp7jhM0i79aDf+pG
	sNdvmtix+qt9WFHyXeQLYw46CUQZk4ehS3Pppww0GsuuWmbe5kc2tk=
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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=9L6mPYu0yeYiiHlkCinlpJPDxm8=; b=FKpD2YzGzoZB9IyEzIt/5KpYt45r
	CCDCgSCqqdNOOkxxuYOvOodDcWO+HXfDNmL0ulij5BwmFYSZTDwYRLcWvY0eYk8E
	BlFpSHnPWAjnktVYDoAm/rusN0+6emvBdh7N+HDpj6mQhXRyHy5zAvwT4U7MpmIr
	UvnwepiMToBZxEo=
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_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+nK78vWUrY3wTK9IfX4b0C
Date: Fri, 7 Mar 2014 00:49:05 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Win32 error 109
Message-ID: <20140307054905.GA890@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAJyLC6tsqKzqDyt6s_pzYOmjx2G834hQO5M7-uABq7RpB7dAgA AT mail DOT gmail DOT com> <CAEotdwnq5Ca6YvzFdNLO65Gb6TEJ_f_QzR7oGCr5_3Qv2bGeOA AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEotdwnq5Ca6YvzFdNLO65Gb6TEJ_f_QzR7oGCr5_3Qv2bGeOA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Mar 06, 2014 at 05:09:18PM -0500, David Conrad wrote:
>On Tue, Mar 4, 2014 at 6:44 PM, Wm. David Bentlage wrote:
>> I occasionally get errors like the following and don't understand
>> what's going on.  Is there a way to correct this?
>>
>> user AT machine /w/dir
>> $ tail -n1 safe*i | grep -i root | wc
>>       6      24     534
>>      70 [main] bash 7012 sig_send: error sending signal -34 to pid
>> 7012, pipe handle 0x98, Win32 error 0
>
>I've also seen this. In fact, I just saw it today, for the first time.
>It happens intermittently.
>
>$ uname -a
>CYGWIN_NT-6.1-WOW64 S1DMZG2 1.7.28(0.271/5/3) 2014-02-09 21:06 i686 Cygwin

Try a snapshot:  http://cygwin.com/snapshots.html

but be aware of the ongoing development from the "Tests needed" thread.  You
can read that thread in the archives here:  http://cygwin.com/ml/cygwin/2014-03/

--
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