Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-Id: <4.3.2.7.2.20010725162832.00bc2a10@san-francisco.beasys.com>
Date: Wed, 25 Jul 2001 16:28:54 -0700
To: Peter Buckley <peter.buckley@cportcorp.com>
From: Andy Piper <andyp@bea.com>
Subject: Re: Degrading tty behaviour
Cc: cygwin@cygwin.com
In-Reply-To: <3B5F30BF.567D36E0@cportcorp.com>
References: <4.3.2.7.2.20010724151409.01766098@san-francisco.beasys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 04:49 PM 7/25/01 -0400, Peter Buckley wrote:
>about this C-c'ing a java process from within bash-
>This was recently discussed with a subject like "ctrl break handling
>in bash and java" or something (IIRC). I don't remember the specific
>message, but search the archives with google. The general gist of the
>problem was that cygwin treats C-c the same as CTRL-BREAK and that was
>bad for java processes started/stopped from the cygwin bash shell.
>Apparently the C-c from cygwin bash killed the java process without
>letting it clean up- it was an interesting discussion.

Thanks

andy


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/