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 Date: Fri, 8 Sep 2000 15:02:01 +0200 (MET DST) From: Bjoern Kahl AG Resy To: Carl Osterwisch cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Bash cpu usage after background task ends In-Reply-To: <20000908124610.49766.qmail@web9404.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit On Fri, 8 Sep 2000, Carl Osterwisch wrote: Hallo ! (Sorry for my english..) > In my experience under the cygwin-1.1.4.tar.gz > package, bash will tie up 100% of the cpu upon > completion of any background task (example: ls &). > This continues until ANY valid key is pressed in the > initiating shell's window, not just the enter key as > has been reported earlier. I like to add, this happens only, if "tty" is set in CYGWIN-environmentvariable. A ps shows the backgroundprocess as ". No command name. I am using cygwin1.1.4, updated on 6.Sept.2000 on NT4 BTW: ssh stops working too, if I have "tty" in CYGWIN-variable It hangs idle for ever, asking for my password. Bjoern Kahl -- +---------------------------------------------------------------------+ | Dipl.-Phys. Bjoern Kahl +++ AG Embedded Systems and Robotics (RESY) | | Informatics Faculty +++ Building 48 +++ University of Kaiserslautern| | phone: +49-631-205-2654 +++ www: http://resy.informatik.uni-kl.de | +---------------------------------------------------------------------+ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com