X-Spam-Check-By: sourceware.org Message-ID: <0706F4CDC397BF4483877BFDA8DBD3A5463148@kjsdemucshrexc1.eu.pm.com> From: "Demmer, Thomas" To: "'cygwin AT cygwin DOT com'" Subject: Re: cygwin 1.5.20 and stalling cygstart Date: Tue, 18 Jul 2006 15:58:25 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com >On Jul 18 03:46, Krzysztof Duleba wrote: >> Corinna Vinschen wrote: >> >> >>WJFFM. I don't see any cygstart processes after running foo or after >> >>calling the perl script directly on the cmd-line. >> > >> >Same here. >> >> Even simpler: >> >> perl -e 'exec "cygstart notepad"' >> >> in Windows command line. > >Nope, not here. > > >Corinna I can confirm Krzystof's behavior. On a DOS cmd (no bash!) line this stalls cygstart. After a while it actually eats up 100% CPU. I have never tried something like that before, invoking cygstart from a cmd window so I cannot tell if this is new. $ uname -a CYGWIN_NT-5.1 KFIDEMUC312022 1.5.21s(0.156/4/2) 20060707 11:45:39 i686 Cygwin $ echo $CYGWIN binmode ntsec smbntsec tty server From Start/Run I get the same behavior. From a bash console window it works as expected. Anything else to try? Ciao Tom -- 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/