Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Fri, 6 Sep 2002 16:38:08 -0500
From:	Steve O <bub AT io DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: orphaned child processes with rxvt
Message-ID:	<20020906163808.A23355@fnord.io.com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5.1i

> If I hit the "close" button in the window rather than typing "exit", rxvt
> cleans up.. but there is still an "ssh" process alive and well sucking up 3
> megs of ram.

I was looking into this last night.  The rxvt source doesn't seem
to do any process management on exit, which says to me that 
the authors expect the child process to die when the parent
dies. 

So the question is, why are rxvt spawned processes under cygwin
detached from their parents, whereas on other systems they aren't.
Any ideas?

-steve


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -