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 Date: Fri, 24 Jun 2005 17:38:02 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Angelo Graziosi cc: cygwin AT cygwin DOT com Subject: Re: Bash 3.0-2 and kill In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Jun 2005, Angelo Graziosi wrote: > I have noted that when one uses > > kill -9 > > in bash 3.0-2 (test), the command kills the process but also bash (even > if one uses /bin/kill...). > > In bash 2.05b-17 that command kills only the process. > > These things happen with > > cygwin 1.5.16-1 > cygwin 1.5.17-1 > snaps. 20050615 > snaps. 20050617 > snaps. 20050621 > > (I have listed only the snaps I tried) > > Which is the normal behaviour (3.0-2 or 2.05b-17)? Unless the refers to the bash process itself, it seems that the behavior of 3.0-2 is wrong. Not sure if it's a bash bug, or a Cygwin signal handling bug exposed by bash (the behavior of /bin/kill seems to point toward the latter). To help debug this, please provide the exact sequence of commands you used to trigger this behavior, as well as the output of "cygcheck -svr" on your system. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/