| Subject: Re: Stopping CLI / SetiSpy from a script |
| From: "Michael D. Ober" <obermd.@.alum.mit.edu.nospam> |
| Date: 08/06/2004, 05:37 |
If you don't have SETISpy set to restart the client, you can use the
"CloseSETIDriver" program to shutdown SETI Driver and the CLI. Go to
http://www.wakeassoc.com/setidriver/additions_and_companions.htm to
download.
Mike Ober.
"Bob" <bobk4000JUNK@JUNKyahooJUNK.JUNKcom> wrote in message
news:40c48f13$0$78543$a1866201@newsreader.visi.com...
I'm running Seti CLI, SetiSpy and SetiDriver on my Windows Server 2000 /
ISA
Server firewall server here at home, with an APC UPS. The UPS service is
set up to shut down the server after running on batteries for 3 minutes.
I've encountered some corruption problems after a UPS shutdown, and I'd
like
to eliminate SETI as a possibility.
What I would like to know is, can the Seti CLI or SetiSpy be shut down
from
the command line gracefully, so it can be incorporated into a script that
is
run when the UPS goes on batteries? I've checked the user guides on
SetiSpy
and didn't find any stop command, and searching the web/groups didn't turn
up anything. SetiSpy does have a Stop button that I've used to stop
processing while updating or rebooting the server manually. While it
might
be possible to come up with a script to find the process ID that Seti is
running under and kill it, I'm looking for something a bit less drastic.
Any thoughts or ideas would be greatly appreciated.
Many thanks,
Bob.