> 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
Greetings, Corinna Vinschen!
> On Feb 15 14:44, Andrey Repin wrote:
>> 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
On Feb 15 14:44, Andrey Repin wrote:
> 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
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
On Feb 14 20:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> Hi all,
>
> It looks like the cygrunsrv utility hardcodes 30 seconds as a maximal time
> for a service to start, then bails
> out with a failure.
>
> It would be quite useful (in certain situations) to have a command-line
Hi all,
It looks like the cygrunsrv utility hardcodes 30 seconds as a maximal time for
a service to start, then bails
out with a failure.
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
6 matches
Mail list logo
