DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=Pue04nfSG1KUNSe07INV0m7L1YmG/BDg9/eeZhppKBGtHjeNxNAO0
	5dTkEu4Y58r3KUb7se5g2pNJS0ly7kDah/ha2UNkNHmFXDSUmG1g6MPidzpa1DkV
	2P/f5KKcYyPHOunq8KYuzJ3w3ro738mKXkk7rzySPKppCP98OJYXyE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epa.gov>
Subject: Re: socat-1.7.3.0-2 fork process sometimes lingers
Date: Sun, 28 Jun 2015 06:47:11 -0400
Lines: 38
Message-ID: <3ljvoa5628b7fj4sih0j164ljum2eft82d@4ax.com>
References: <5583B6D2.5000602@yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> socat-1.7.3.0-2
> Cygwin 2.0.4(0.287/5/3)
> Windows 7 x64 SP1
> 
> Since upgrading socat today I've noticed that when I CTRL+C to terminate 
> it sometimes the spawned process won't terminate. For example open two 
> Cygwin terminals and:
> 
> In one:
> socat tcp-listen:8080,reuseaddr,fork -
> 
> And then in the other:
> nc localhost 8080
> 
> In the one where socat is running CTRL+C. It will appear to end but 
> sometimes the spawned process lingers. When that happens nc will not 
> terminate either and the connection still shows as established (even 
> though the parent process which supposedly held the connection has 
> ended). This is not exclusive to nc I have this same problem with the 
> client applications I am using to connect to socat. They think the 
> connection is still established so they won't end.
> 
> It may take a couple of tries to reproduce. I can reproduce about 20% of 
> the time.
> 
> I cannot reproduce using the socat.exe from socat-1.7.2.4-1.
> 
> The cygcheck has too much personal information but I have attached the 
> package versions section.

Thanks for reporting.  I don't have any immediate insight into what's causing
this, or any time right now to try to reproduce or debug it.  I'll look at it as
soon as I can.

I've recently observed similar behavior in screen, so I suspect that it could be
a cygwin problem.  But I'll need some time to run that down.

Andrew


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