Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-WM-Posted-At: avacado.atomice.net; Sat, 20 Apr 02 01:27:56 +0100
Message-ID: <00ad01c1e802$37c1f040$0100a8c0@advent02>
From: "Chris January" <chris AT atomice DOT net>
To: <cygwin AT cygwin DOT com>
References: <002201c1e7f6$cb2c8c70$651c440a AT BRAMSCHE>
Subject: Re: Offer for killall-script
Date: Sat, 20 Apr 2002 01:27:55 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

> In the cygwin-apps I have seen some messages
> http://sources.redhat.com/ml/cygwin-apps/2002-01/msg00340.html about a
killall
> util, which was going to be part of the cygutils packages but was waiting
> because of licensing problems.
>
> For killall I'm using a good working script for about a half year. Perhaps
> anyone like this to integrate in the cygutils package. This script allows
> killing more than one task, because it does a grep with the first param.
>
> syntax: killall <taskname> | <tasknamepart>
>
>
> $ cat /bin/killall
> ps -ea | grep $1 | gawk '$1 ~ /^[^SI]/ { system("kill -9 " $1); }'
See Randal's "Usesless Use of kill -9" posts...
http://groups.google.com/groups?q=insubject:useless+insubject:use+insubject:
kill&hl=en&selm=8cpw0y2gb2.fsf_-_%40gadget.cscaper.com&rnum=1
i.e. the signal sent should be configurable :-)

Regards
Chris



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