Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 2 Mar 2003 12:43:28 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Processes are unable to fully discard their controlling terminal Message-ID: <20030302174328.GD441@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <001b01c2e0d1$2393a320$78d96f83@pomello> <20030302173304.GC441@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030302173304.GC441@redhat.com> User-Agent: Mutt/1.5.1i On Sun, Mar 02, 2003 at 12:33:04PM -0500, Christopher Faylor wrote: >On Sun, Mar 02, 2003 at 03:33:56PM -0000, Max Bowsher wrote: >>Processes that attempt to shed their controlling terminal do so well enough >>for the tty to show as ? in ps output, but they still keep the console >>window they were launched from open, after all other processes using it have >>exited. >> >>This is particularly annoying with ssh-agent - if I exit the shell in the >>terminal that launched it, that terminal becomes a zombie, hanging around >>for no purpose. If I close that window using the Windows close box, the >>ssh-agent is killed. >> >>I'm not an expert in the ways of Unix ttys. Can anyone help me understand >>where the problem lies? > >setsid() I think I see the problem. It will be tricky to fix but I'll see what I can do. cgf -- 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/