| Subject: Stopping CLI / SetiSpy from a script |
| From: "Bob" <bobk4000JUNK@JUNKyahooJUNK.JUNKcom> |
| Date: 07/06/2004, 16:51 |
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.