Message-Id:	<200508120913.j7C9DCXf008733@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Herb Martin" <HerbM AT learnquick DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Remove cygwin services
Date:	Fri, 12 Aug 2005 04:13:10 -0500
MIME-Version:	1.0
In-Reply-To:	<loom.20050812T103036-663@post.gmane.org>

> root AT ITO2 ~
> $ cygrunsrv.exe -R init
> cygrunsrv: Error removing a service: QueryServiceStatus:  
> Win32 error 1053:
> The service did not respond to the start or control request 
> in a timely fashion.
> 
> 
> By root, I mean this is an administrator a/c.	

As I understand cygrunsrv, when you remove a service it
also assumes you wish to stop that service.  If the service
refuses to stop -- which isn't that uncommon for services
started under cygrunsrv (for testing) since they don't know
they are "services" -- then you will see that error.

I believe that cygrunsrv has already changed the registry
(unconfirmed) and therefore the service will be gone on
next boot.  (If not, I would consider this a bug in cygrunsrv.)

It might help (pure speculation) to enable one of the "signals"
when creating Cygwin-Apps as services.  This way the "stop"
will include a HUP or TERM.

--
Herb Martin


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

- Raw text -