DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:reply-to:to:subject:date:message-id
	:references:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=XwsZyoYhq3DOkaR+iUyZ1Yl1Ismdh
	q2/tTGOHx5P+6VGGdJN3VWrilJmP39BNgDhdZASvWIwwGX4mv0YXpfxJgHNZkMk7
	bno4ZNqElmXSglGcEk51J0fuT96ND0MAy14mIRKnOUmlXyKHeRXPql3AIU5MtlxX
	qDjVUnJsYZ1lLo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" <cygwin@cygwin.com>
Reply-To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: cygrunsrv to have a timeout parameter for service startup
Date: Fri, 15 Feb 2019 14:52:41 +0000
Message-ID: <BL0PR0901MB3236B533598BF41042D161BFA5600@BL0PR0901MB3236.namprd09.prod.outlook.com>
References: <BL0PR0901MB3236D41983198109E0643AE7A5670@BL0PR0901MB3236.namprd09.prod.outlook.com> <471075939.20190215144447@yandex.ru>
In-Reply-To: <471075939.20190215144447@yandex.ru>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

> No, 30 seconds is a hard system timeout in which a service must reply with
> an appropriate control message to let services.exe know it is ready to
> continue startup sequence.

I don't think there is a hard-coded system timeout, as long as the starting service keeps
posting its START_PENDING status, the service controller will wait.
And cygrunsrv seems to be doing that already.

MSDN doc says exactly that.  And I've also seen some articles that tell the same.

https://docs.microsoft.com/en-us/windows/desktop/api/winsvc/nf-winsvc-setservicestatus

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