🚀 go-pugleaf

"Ted Lyngmo" <MY_FIRST_NAME@lyncon.se> wrote in message
news:3ED44056.8080702@lyncon.se...

> "A service cannot call StartService during initialization. The
> reason is that the Service Control Manager locks the service
> control database during initialization, so a call to StartService
> will block. Once the service reports to the Service Control
> Manager that it has successfully started, it can call StartService."

Hmm, didn't see that notice before.  That would make sense then.  Damn, that
doesn't help me then, because I need to call StartService() near the
beginning of my other service's initializations, not at the end of it.  Oh
well, back to the drawing board...

> Might be worth checking out, even though it sounds like
> it's not the actual cause (since your second service starts
> immediately).

Yeah, but StartService() is taking several minutes before even attempting to
start the second service.  Once it actually does, though, then it goes by
quickly as expected.  Having the SCM database locked by the first service's
startup makes sense, though.  The delay is probably in the SCM waiting for
the DB to be unlocked so it can lookup up the second service's executable
path and such, and the first service is blocked on StartService() and
eventually times out so the SCM unlocks itself and proceeds after the
timeout.

> When starting the simple services from within the control
> panel, do they start immediately?

Yes.

> Do you get the same effect when starting standard Windows
> services from within your service?

Haven't tried that yet.  I suspect it'll fail as well, as per the comments
above.


Gambit