Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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 16:47:53 -0500 (EST)
Message-Id: <200303072147.h27Llr8Q012503@skunk.nvs.com>
From: "Richard H. Broberg" <rhb AT inficon DOT com>
To: cygwin AT cygwin DOT com
Subject: cygwin/1.3.20-1 bash child process disassociation behavior weirdness


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.

The easiest way to test this is:

in 1 window:

$ sleep 60 &
$ exit
logout

(parent process (shell window) will not exit until after the child process
is complete, 60 seconds later)

Also, this doesn't seem to be limited to bash; I get the same behavior
in tcsh.

Is there something I need to do to cause bash to properly disassociate itself
from child processes so that I get get commands to run in the background
and leave my shell?

--
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/