X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=1.2 required=5.0 tests=AWL,BAYES_00,DATE_IN_FUTURE_03_06,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
X-Authority-Analysis:	v=2.0 cv=eq5dP/VX c=1 sm=0 a=BYtf1cvtHDi0yqkswXf3ig==:17 a=N1BqOr4lPycA:10 a=enQhnZMI4hwA:10 a=05ChyHeVI94A:10 a=8nJEP1OIZ-IA:10 a=w_pzkKWiAAAA:8 a=xyGQxoX4HjATa4OiR1sA:9 a=wPNLvfGTeEIA:10 a=buB1NfXUTBUA:10 a=IfQ-iFkkCvMA:10 a=BYtf1cvtHDi0yqkswXf3ig==:117
Message-ID:	<4FA3FE56.5030504@cfl.rr.com>
Date:	Fri, 04 May 2012 09:05:42 -0700
From:	"eric_justin_allan AT cfl DOT rr DOT com" <eric_justin_allan AT cfl DOT rr DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1
MIME-Version:	1.0
To:	Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: Question about kill
References:	<4FA3CA9D DOT 3040408 AT cfl DOT rr DOT com> <4FA3C2C5 DOT 7020306 AT gmail DOT com> <4FA3C77B DOT 2040901 AT redhat DOT com> <4FA3C88B DOT 50103 AT gmail DOT com>
In-Reply-To:	<4FA3C88B.50103@gmail.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Well kill program_name didn't work and kill -9 is pretty much what I am 
looking for.
Does it matter if you are gonna overwrite the program if you use kill -9?


marco atzeri wrote:
> On 5/4/2012 2:11 PM, Eric Blake wrote:
>> On 05/04/2012 05:51 AM, marco atzeri wrote:
>>
>>>
>>> Usually
>>>    kill -9 your_program_name
>>>
>>> works very well
>>
>> Usually 'kill -9 your_program' is overkill; it forcefully terminates the
>> program with SIGKILL, which means the program has no chance to clean up
>> after itself, and can leave your file system in a mess for the next time
>> you attempt to run the program.  You should reserve this for a
>> last-ditch effort, only after the nicer 'kill your_program' (SIGTERM) or
>> 'kill -s INT' (SIGINT) both result in no action.
>>
>
> I had the impression he needs the last resort...
>
> -- 
> 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
>
>


--
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

- Raw text -