If we make a service (NT Service) dependent on another service.
If a service is stopped, the services that depend on that service
are also stopped. When you start a service, the SC Manager
automatically starts services on which the selected service is
dependent.
The objective is to prevent the Workstation service from
terminating before XXX services during shutdown. During
shutdown, the service dependencies are ignored. By default,
each service has 20 seconds to shut down. This default can
be changed by implementing and Control Handler Function.
If the service needs to take more time to shut down, it
should send out STOP_PENDING status messages, along with
a wait hint, so that the service controller knows how
long to wait before reporting to the system that service
shutdown is complete.
I believe that we need XXX service to set a hook for the
Workstation service in order to prevent it from stopping
prematurely during shutdown. Does anyone have an idea how
this could be achieved or any other alternative?
We want this desired order?
Start Order: Workstation Service -> XXX Service
Stop Order: XXX Service -> Workstation Service
Mike
Get free email and a permanent address at http://www.amexmail.com/?A=1
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com