Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Thu, 8 Nov 2001 10:46:32 +0100
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygrunsrv v0.94 starts but not stops java.exe
Message-ID:	<20011108104632.E2965@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<000301c1681e$107fc0c0$2ae61718 AT bdfrd1 DOT tx DOT home DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<000301c1681e$107fc0c0$2ae61718@bdfrd1.tx.home.com>; from jle@post.com on Thu, Nov 08, 2001 at 12:24:47AM -0600

On Thu, Nov 08, 2001 at 12:24:47AM -0600, Joshua wrote:
> >     I'm trying to use cygrunsrv to run a java application.  It will start
> > the application just fine, but will not stop it.  Initially, I thought
> that
> > java.exe was acting like a typical UNIX forking daemon as described in the
> > readme and the web.  However, if I understand that problem correctly, it
> is
> > indicated by the cygrunsrv processes dying immediately after they are
> > started?  My cygrunsrv processes do not die until I kill them or the
> > corresponding java.exe process.  If I kill either of the cygrunsrv
> > processes, both die, but the java.exe process lives on.
> >
> >     Now, I'm leaning towards cygrunsrv not sending the correct signal to
> > java.exe to get it to shutdown or java.exe not accepting the signal.  If I
> > run the java app from the command line, a simple CTRL-C stops it.  I tried
> > the basic signal (TERM, HUP, INT, QUIT) with no effect.  Please see the
> > screen capture below.  Any help or references would be
> > appreciated...BCNU//jle

Java.exe is not a Cygwin application, right?  So it doesn't understand
the Cygwin signal mechanism.  Cygrunsrv is created to support Cygwin
applications so only the signals are sent to the service application
to stop it.  If the application doesn't stop, cygrunsrv doesn't stop
as well.

We could perhaps add a `force' option for killing the application
as in kill.exe.  Patches gratefully accepted.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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

- Raw text -