From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126842 invoked by alias); 15 Feb 2019 11:50:10 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 126750 invoked by uid 89); 15 Feb 2019 11:50:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=HX-Priority:Normal, english, H*M:yandex, H*UA:Bat! X-HELO: forward103p.mail.yandex.net Received: from forward103p.mail.yandex.net (HELO forward103p.mail.yandex.net) (77.88.28.106) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 Feb 2019 11:50:07 +0000 Received: from mxback16g.mail.yandex.net (mxback16g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:316]) by forward103p.mail.yandex.net (Yandex) with ESMTP id 6B4AF18C0962; Fri, 15 Feb 2019 14:50:03 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback16g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id IoMmhvRDol-o380K59j; Fri, 15 Feb 2019 14:50:03 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1550231403; bh=1hT9q3lfn5m/47M589LwDBZPV/TpsVWVrXBL3fiWa6c=; h=Date:From:Reply-To:Message-ID:To:Subject:In-Reply-To:References; b=nmsOBl8lS0wOgOTn0i2yN4kTUUgc3EjUAYMbkX+GLdgxjNbdvJLKPEcGTbh5caue3 SH7+Ze/uV7oCSTMLJ/muG1V3rv+4hbO4SWTkZay1YTatSwUCW8mL4e5eAKifrq2mma zY5o4WTGJjDGKWeraaWvyUuNZwj8MQdjgb2pALQQ= Authentication-Results: mxback16g.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id cRgLfKZ94H-o2c0FMjm; Fri, 15 Feb 2019 14:50:02 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Fri, 15 Feb 2019 11:44:47 -0000 Date: Fri, 15 Feb 2019 11:50:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <471075939.20190215144447@yandex.ru> To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" , cygwin@cygwin.com Subject: Re: cygrunsrv to have a timeout parameter for service startup In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00176.txt.bz2 Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]! > It looks like the cygrunsrv utility hardcodes 30 seconds as a maximal time > for a service to start, then bails out with a failure. 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. > It would be quite useful (in certain situations) to have a command-line > parameter (for the -I option) that can specify a service startup timeout, > longer or shorter than the preset default. Is there such a feature at all to begin with? A link to MSDN would suffice. -- With best regards, Andrey Repin Friday, February 15, 2019 14:42:40 Sorry for my terrible english... -- 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