[DUG] Stopping particular services, alternative to services.

[Phil Scadden]

Okay, here is the picture. Have a application that does continuous real-time
data processing on Windows Server. I need several copies of this application
running at the same time, each distinguished by different startup parameters.
I need to be able to have several of these started on server boot and also
to be able to start/stop these processes from an interactive session on 
the server. The application must continue even if session logs out.

So, all that sounds like service application. Pain though because the application
needs network resources too.

Q1 - if using services, I might start the service with parameter =1 for one,
parameter=2 for second etc. How do I identify the service session to halt
though when I want to say terminate the service that was started with
parameter=2? Can I use a service name here to distinquish?

Q2 - Is there an alternative to services? I can start up a process at poweron
with the scheduler service but is there a way to start an application that
isnt a service so that it survives user logout?
----------------------------------------------------------
Phil Scadden, Institute of Geological and Nuclear Sciences
764 Cumberland St, Private Bag 1930, Dunedin, New Zealand
Ph +64 3 4799663, fax +64 3 477 5232