Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<4162B4F1.4646248D@dessent.net>
Date:	Tue, 05 Oct 2004 07:51:29 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Run program in background.
References:	<64AE3D5B518E3648ACC823FBCB0B737502A6B3FB AT sr002-2kexc DOT ateb DOT com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Reid Thompson wrote:

> > If you just want your program to simply run in the
> > background, launch it with a "&" at the end of the command
> > from the shell.  However, if it expects to use stdout, stdin,
> > or stderr, it will stop -- so these must all be redirected to files
> > or pipes.
> 
> not exactly correct the program does not stop, stdin is not accessible
> via the shell, but stdout and stderr are by default, still routed to it.

You're correct.  I guess what I mean to say was that it will stop if it
tries to read stdin, and for the sake of the user at the console stdout
and stderr will need to be redirected to prevent screen pollution.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -