I believe the whole purpose of the request is being
misconstrued.
The idea was so that someone could not log onto the
serversalive server and launch another instance of SA not to check if it is
running.
We have instances where technicians will double click the
executable and launch SA a second time.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pech Lukas (CZ)
Sent: Friday, November 25, 2005 2:37 AM
To: salive@woodstone.nu
Subject: RE: [SA-list] Feature request
Some products solved this issue by adding a kind of
"Watchdog" service. It just periodically checks if the main service is runnig
and starts it in case of any problem.
This could be a solution.
Lukas
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Wednesday, November 16, 2005 4:10 PM
To: salive@woodstone.nu
Subject: RE: [SA-list] Feature request
Theoretically this is possible.
But this is not something we want to make/do as running
service and app at the same time can give weird issues.
Dirk.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dolinar, Jon
Sent: Wednesday, November 16, 2005 3:32 PM
To: salive@woodstone.nu
Subject: [SA-list] Feature request
Is it possible for the Serversalive executable to check to see if the Serversalive Service is running and if not start the service? If it is just bring up the GUI already running?
I know
if you try to just run it twice as a non service it will give you an error
that it can be only run once but if the following situations occur you can run
into problems.
If the
service is running you can start another instance of SA by running the
executable.
If the
executable is running you can start another instance by starting the
service.
John
Dolinar
Manager, Network Security
Cuyahoga Community College
