X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 7 May 2012 16:58:40 -0400 Message-ID: Subject: nohup...ampersand behaviour From: Charles Stepp To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 I'm not sure when it started, but I've noticed that the parents of processes that have been nohup'd and ampersanded into the background hang after 'exit' until their children go away. I'm aware of the interactive shell's prompt warning about background processes running, but I've never had processes wait unconditionally until after their children are gone if the children are nohup'd and ampersanded. Come to think of it, I had a child die when it's parent was interrupted with ctrl-c. Anybody have any idea. This finally became too irritating to ignore, since I like to have a real mess of windows floating around. Charles Stepp -- 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