From:	earnie_boyd AT hotmail DOT com (Earnie Boyd)
Subject:	RE: bash and '&'
9 Apr 1998 02:49:12 -0700 :
Message-ID:	<19980407194457.22309.qmail.cygnus.gnu-win32@hotmail.com>
To:	earnie_boyd AT hotmail DOT com, wku1 AT utk DOT edu, sos AT buggy DOT prospect DOT com DOT ru
Cc:	gnu-win32 AT cygnus DOT com

>From: Sergey Okhapkin <sos AT buggy DOT prospect DOT com DOT ru>
>To: Earnie Boyd <earnie_boyd AT hotmail DOT com>, "'Wei Ku'" <wku1 AT utk DOT edu>
>Cc: "gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>
>Subject: RE: bash and '&'
>Date: Tue, 7 Apr 1998 21:58:41 +0400
>
>Wei Ku wrote:
>> I got the exactly result from b19. Ghostview& is still alive after 
exit from
>> bash. However, the console window does not disappear until Ghostview 
is
>> closed. This is slightly different from the situation in true UNIX 
machine.
>> 
>> I would guess that Mr. Sergey Okhapkin has a clear idea why the 
console
>> window is still there.
>> 
>
>It's very easy - cygwin-compiled ghostview is a _console_ application! 
It has console buffer allocated and console handles opened.

You are not understanding the problem.  If in b18 bash you execute a job 
in the background, say for example "wish80 &", and exited the bash 
session then the TK window remained open and the console window died.  
If you do the same thing under b19, the bash process dies but the 
console window doesn't.  You can't do anything with it except to iconize 
it and wait until your done with TK.  When you exit TK then the dead 
window will disappear.


>
>-- 
>Sergey Okhapkin, http://www.lexa.ru/sos
>Moscow, Russia
>
>
>


-        \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd AT hotmail DOT com-
------ooo0O--O0ooo-------



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
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 -