delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/11/06/23:31:51

From: Pierre DOT Humblet AT eurecom DOT fr (Pierre A. Humblet)
Subject: Re: Bash exits after background command exits (B20)
6 Nov 1998 23:31:51 -0800 :
Message-ID: <3.0.5.32.19981105202047.00882d30.cygnus.gnu-win32@pop.ne.mediaone.net>
References: <3640B2BB DOT B75A5AF5 AT transcanada DOT com>
Mime-Version: 1.0
To: "Neil Schemenauer" <neil_schemenauer AT transcanada DOT com>,
gnu-win32 AT cygnus DOT com

At 01:02 PM 11/4/98 -0700, Neil Schemenauer wrote:
>For some reason bash is getting a EOF after a background command exits. 
>To keep bash open IGNOREEOF can be set to 1.  This prints "Use "exit" to
>leave the shell." after every background command exits.  Annoying. 
>Also, Control-C seems to still kill background tasks.  Setting
>CYGWIN=tty does not seem to help.  Finally, bash doesn't exit if there
>are background tasks running.  Help!
>
My experience with B20 on my Win95 box, CYGWIN=tty, is that bash will
freeze (not exit) after the last background command exits (well, 90% of the
time...), irrespective of IGNOREEOF....
Thus
sleep 10 &
sleep 20 &
(almost) guarantees a freeze in 20 secs.

Pierre

>
>	Neil
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019