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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <38876DC8.1340D6B5@burkby.com> Date: Thu, 20 Jan 2000 15:19:20 -0500 From: Joe Burpee Organization: Burkby Consulting http://www.burkby.com X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com Subject: Start background process under bash Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have a bash script in which I start another script in the background with the usual bgJob & Works fine under Linux. Under Cygwin b20.1 with Win95/98 I get an annoying "illegal operation" popup every time, but the thing runs in the background ok anyway, and the calling script continues in parallel. As a workaround for the illegal op, I switched to using the following in my bash script command.com /c start bash "bgJob" It seems to me this just tells the DOS shell to do essentially the same thing, and everything works ok, no popup. Any number of processes seem to run just fine in parallel. Then I switched to NT4 (where the start command has slightly different switches from Win9x). Neither of the above works. No popup, but the calling script always *waits* for the background process, which doesn't make a helluva lot of sense. I assume the start command syntax is off-topic in this list, but I would be interested if anyone knows what's wrong with "bgJob &". Or if anyone has another workaround for bash/Cygwin under NT, I would be very pleased to hear about it. Joe -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com