Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 7 Mar 2003 17:11:02 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin/1.3.20-1 bash child process disassociation behavior weirdness Message-ID: <20030307221102.GD30394@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200303072147 DOT h27Llr8Q012503 AT skunk DOT nvs DOT com> <038a01c2e4f4$fbd8fc90$78d96f83 AT pomello> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <038a01c2e4f4$fbd8fc90$78d96f83@pomello> User-Agent: Mutt/1.5.1i On Fri, Mar 07, 2003 at 10:00:28PM -0000, Max Bowsher wrote: >Richard H. Broberg wrote: >> In non-cygwin unix I'm familiar with being able to do the following >> in a shell (bash or other): >> >> $ nohup long-running-command & >> $ exit >> >> and be able to leave it running. >> >> However, under cygwin (this has been true for at least back to >> cygwin/1.3.6 for me), when I start a process in the background and >> try to exit >> my bash shell, it hangs until the child process completes (almost as >> if it's doing a wait() on its children). >> >> Additionally, if I start a command nohup in the background in 1 bash >> shell and close the window, it kills the child process. > >An unfortunate consequence of how Windows handles console windows. This works for me: nohup sleep 30 foo 2>&1& at least with the latest version of cygwin... 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/