Gentlemen,
Is there any way to enforce service start order?
XP starts services following entries in registry.
Is there any way to change the order?
One obvious thing to do is to follow Unix rules and leave files
in /var/run (or temp) or just probe each previous service to open.
Is there any other way to do it?
–
Regards,
Alex
If you mean services rather than device drivers, then yes you can specify dependencies such
that service A starts after service B and will not start if B fails to start. See the Service
Control Manager API in the Platform SDK.
===========================
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032
-----Original Message-----
From: Alex Ivchenko
To: “NT Developers Interest List”
Date: Mon, 27 Jan 2003 13:32:26 -0500
Subject: [ntdev] Service start order
> Gentlemen,
>
> Is there any way to enforce service start order?
> XP starts services following entries in registry.
> Is there any way to change the order?
>
> One obvious thing to do is to follow Unix rules and leave files
> in /var/run (or temp) or just probe each previous service to open.
> Is there any other way to do it?
>
> –
> Regards,
> Alex
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hollistech.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
> Is there any way to enforce service start order?
Surely, this is enforced by DependsOnService and DependsOnGroup
registry values.
The only exception is PnP drivers. Their start order cannot be
enforced.
One obvious thing to do is to follow Unix rules and leave files
in /var/run
Terrifying outdated technology.
Max