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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: cygwin/1.3.20-1 bash child process disassociation behavior weirdness Date: Sat, 8 Mar 2003 00:44:29 +0100 Lines: 42 Message-ID: References: <200303072147 DOT h27Llr8Q012503 AT skunk DOT nvs DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: 40tude_Dialog/2.0.3.1 * Richard H. Broberg (03-03-07 22:47 +0100) > 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? Use rxvt. Thorsten -- Content-Type: text/explicit; charset=ISO-8859-666 (Parental Advisory) Content-Transfer-Warning: message contains innuendos not suited for children under the age of 18 -- 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/