X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_20
X-Spam-Check-By:	sourceware.org
Message-ID:	<962898.14837.qm@web30805.mail.mud.yahoo.com>
Date:	Thu, 5 Nov 2009 03:50:25 -0800 (PST)
From:	"Larry W. Virden" <lvirden AT yahoo DOT com>
Subject:	Halting JBoss under Cygwin
To:	Cygwin <cygwin AT cygwin DOT com>
MIME-Version:	1.0
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

One of the developers trying out Cygwin recently asked me for some assistance regarding the bringing of JBoss to a halt.

Previously, he had been using MKS Toolkit. His process is run a .bat file that starts up the JBoss application server, which also starts his application. Then, under MKS Toolkit, he could use ps and kill to locate the appropriate processes and kill them when he needed.

As he has begun testing JBoss under Cygwin, he has had some problems getting things to work. The first problem was that the processes were not showing up in ps. I found the mention in the ps man page concerning the use of -W to see Windows processes, and that helped some. Now he can see the processes using ps -Wef. However, when he issues a kill against the process id, kill says the process doesn't exist.

Is there some material to which I can point the developer to help him over this hurdle?

Thank you all very much.


      

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