delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/11/02/09:50:01

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <DFF041EA401381429D93751BE9CE54780523CD@direxch1>
From: Barry Buchbinder <BBUCHBINDER AT niaid DOT nih DOT gov>
To: "Cygwin (E-mail)" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Starting Programms in the background
Date: Thu, 2 Nov 2000 09:42:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)

Corinna Vinschen wrote

>klaus DOT berndl AT sdm DOT de wrote:
>> 
>> If i start a program in the background from bash (e.g. "winword.exe
<document> &") then
>> all is working fine. But if i try to exit from the bash-shell from which
i have started the program
>> before i have finished the program then bash writes "logout" but doesn't
terminate until i terminate
>> all previous started programs.
>>
> How can this be avoided, means how to exit bash regardless of any still
running background programs?
>
>Never, I fear. It sounds as if you are running some 9X system. It's
>a problem of all 9X console windows that you can't close the window
>unless all child processes are killed. If you want to run daemons
>invisible you'll have to start them by using a shortcut with the
>minimized state set.
>
>Corinna
>
>-- 
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Developer                        mailto:cygwin AT sources DOT redhat DOT com
>Red Hat, Inc.
>mailto:vinschen AT redhat DOT com

On my win98 machine, one can start winword from a command.com DOS box and
exit the DOS box before exiting winword.  bash behaves as described above,
whether or not "&" is used.  However, from bash I can launch winword using
the start command (c:\windows\command\start.exe) and then exit bash.  This
is probably because start.exe exits after launching winword.  I didn't see a
difference between launching winword.exe and winword.lnk.  "&" makes no
difference.  One can control how the program opens and whether start exits
immediately.

500 /cygdrive/c> start /?
Runs a Windows program or an MS-DOS program.

START [options] program [arg...]
START [options] document.ext

/m[inimized] Run the new program minimized (in the background).
/max[imized] Run the new program maximized (in the foreground).
/r[estored]  Run the new program restored (in the foreground). [default]
/w[ait]      Does not return until the other program exits.
501 /cygdrive/c>

Of course you can just start winword the windows way.

- Barry Buchbinder

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


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