This is the mail archive of the
mailing list for the Cygwin project.
Re: orphaned child processes with rxvt
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 6 Sep 2002 17:41:16 -0400
- Subject: Re: orphaned child processes with rxvt
- References: <20020906163808.A23355@fnord.io.com>
- Reply-to: cygwin at cygwin dot com
On Fri, Sep 06, 2002 at 04:38:08PM -0500, Steve O wrote:
>> 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
>So the question is, why are rxvt spawned processes under cygwin
>detached from their parents, whereas on other systems they aren't.
In theory, child processes in a process group should be receiving a SIGHUP
on exit. Does ssh die on a SIGHUP?
Running rxvt under strace might be instructive.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html