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
Date: Sun, 6 Jul 2003 20:37:15 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: the "kill" command
Message-ID: <20030707003715.GA30559@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OFCE1D8A5F DOT E78CAC3E-ON85256D5C DOT 00018CB6-85256D5C DOT 000239CE AT empirehealthcare DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OFCE1D8A5F.E78CAC3E-ON85256D5C.00018CB6-85256D5C.000239CE@empirehealthcare.com>
User-Agent: Mutt/1.4.1i

On Sun, Jul 06, 2003 at 08:24:12PM -0400, Brian DOT Kelly AT Empireblue DOT com wrote:
>
>You have a point. I cannot kill some windows in processes "directly" within
>the bash environment either.
>But this works EVERY time:
>
>      cmd   /c  kill  --force   <PID>
>
>Try it, you'll like it.

Or, you could just do what I suggested, which is much easier than the above.

>p.s. It'd be nice if it worked "as advertised"   ;-)

It works as advertised.  You just have to meditate on the difference between
a bash built-in and an actual program like /bin/kill.exe .

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