RE: cygrunsrv to have a timeout parameter for service startup

2019-02-15 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
> 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 st

Re: cygrunsrv to have a timeout parameter for service startup

2019-02-15 Thread Andrey Repin
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 sy

Re: cygrunsrv to have a timeout parameter for service startup

2019-02-15 Thread 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 system timeout in which a service must r

Re: cygrunsrv to have a timeout parameter for service startup

2019-02-15 Thread Andrey Repin
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 s

Re: cygrunsrv to have a timeout parameter for service startup

2019-02-15 Thread Corinna Vinschen
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