>Sniffer is adaptive. You can turn the persistent instance on and off at >will. Simply stop the service - a reboot is not needed. If the persistent >instance is turned off then the remaining instances will organize >themselves in the usual way.
I don't have it running as a service, I started the persistant instance via command line.
That's fine... I nearly forgot something important anyway.
sniffer.exe stop - will stop the persistent server by sending it a message file.
Run 'sniffer.exe stop' at the command line and your persistent instance will exit cleanly on it's own. [ replace sniffer.exe with the name of your executable of course ]
If you are running it from the command line then it will stop before the command returns.
To restart it simply run your persistent command line again.
For those running as a service....
If you are running it as a service, the persistent instance will stop - possibly under the service stub. If this is the case (as with RunExeSvc) then you will need to stop and start the service when you are ready to bring it back.
_M
PS: If you do just kill the persistent instance it will leave it's .SVR file behind and will abandon the job it is doing. While this is unkind, it will not be a problem - the normal peer-server instances will quickly clean out the stranded .SVR file and the abandoned job will be handled by the client instance when it gets tired of waiting.
This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
