Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A013FC0.340472FC@redhat.com> Date: Thu, 02 Nov 2000 11:19:44 +0100 From: Corinna Vinschen Reply-To: cygwin AT sources DOT redhat DOT com X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygwin Subject: Re: AW: Starting Programms in the background References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit klaus DOT berndl AT sdm DOT de wrote: > > > 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. > > No, im using Windows NT!! Ooops, sorry, I was so sure that this only happens on 9X that I haven't proved it on NT. You're right, it happens on NT as well when starting background processes from the console window. This does not happen when starting background processes from a remote session via telnet/ssh. Unfortunately you can't start GUI processes from a remote session. 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 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com