X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 5 Apr 2010 17:35:50 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cannot stop "cygcheck -c" Message-ID: <20100405213550.GA11775@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4BBA4E05 DOT 8030602 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BBA4E05.8030602@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Mon, Apr 05, 2010 at 02:54:29PM -0600, Eric Blake wrote: >On 04/05/2010 02:54 PM, Tim McDaniel wrote: >> I'm running the latest setup.exe, cygwin libraries, and installed >> packages. I ran "cygcheck -c" (thanks to the list member who pointed >> it out). After a screen or two, I wanted to stop the output to scroll >> back. It doesn't seem to respond to control-C or control-Z. Does >> this happen to anyone else? > >Yes, this is an unfortunate side-effect of cygcheck being a native >windows program rather than a cygwin app. It doesn't know how to >respond to cygwin signals. That shouldn't matter. If you're running it from bash then CTRL-C should still terminate the process unless there's a bug. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple