X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40 X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4B90E4BC.5050808@towo.net> References: <201002261446 DOT o1QEki2k024924 AT mail DOT bln1 DOT bf DOT nsn-intra DOT net> <416096c61002261229j31f92387u8b8e3e9b716cb131 AT mail DOT gmail DOT com> <4B8BEACA DOT 4010003 AT towo DOT net> <416096c61003032349h6f22d223v7aa03c07f4f27475 AT mail DOT gmail DOT com> <4B90E4BC DOT 5050808 AT towo DOT net> Date: Fri, 5 Mar 2010 21:19:12 +0000 Message-ID: <416096c61003051319r5e87a7bcye90a9f15ad17c6d1@mail.gmail.com> Subject: Re: terminals getting killed on parent's termination From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Thomas Wolff: > Termination of a terminal's parent. This should not abort the terminal > session, whether or not the notification mechanism is HUP. (In the case > console -> xterm you said it's due to console attachment, whatever that > means in detail.) Well, in practical terms it means that xterm would need to call FreeConsole() to detach from the console it's started from. If you're interested in the details, there's always MSDN. Andy -- 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