HI Pete,
I uploaded the new .exe file, renamed it to my number.
I don't get this persistant instance thing...can you give this to me in laymans terms? Im just a simple network engineer with 17 years of experience. How do I get it working? I need an example..
Thanks, andy :) Thumpernet
First, treat this like a normal upgrade - looks like you did that part.
Now, a little background so you will know what's going on...
Under normal conditions your mail server will create one instance of Message Sniffer for each message.
Usually this means that more than one of these might be running at once.
Beginning with version 2-2, when more than one of these is running at the same time the group will coordinate to elect one of them as a server so that the others can be clients and avoid loading the rulebase. This is cellular peer-server technology. This speeds thins up a lot and reduces the loads on the server.
Although cellular peer-server technology makes things very efficient, there are still some times that more than one instance might elect to be a server, and under lower system loads when only one message at a time is being processed that could mean the rulebase is loaded for every message. This can slow down other processes on your server... Also, if you are running a system that somehow will only scan one message at a time through Message Sniffer you will be guaranteed to load the rulebase every time because there will never be more than one instance running. So... there is clearly room for improvement.
Beginning with version 2-3, you can launch an instance of Message Sniffer outside of your mail server and run it in "persistent" mode. This instance will look to the others like it has already been elected as the server - so every time your mail server launches an instance to process a message, that instance will elect to be a client and so it will not load the rulebase.
In version 2-2, and in 2-3 when there is no persistent instance running, server instances show up as needed to save a good deal of computing power and make things go quickly on the server. Version 2-3 implements the same cellular peer-server technology as version 2-2.
However, with version 2-3 when a persistent instance is running then messages are always processed by clients so things are very efficient and a bit more predictable. The persistent instance "tricks" the peers into following a client-server model. For safety, if the persistent instance crashes or goes away for some reason then things drop back to "normal".
To take the second step and use persistence - you need to run one extra instance of Message Sniffer and replace the message file name on the command line with "persistent". This instance will stay alive between messages and act as a persistent server.
On Win32 systems you can run this instance as a service using the Win 2K toolkit or a utility like FireDaemon, or RunSvcExe. Unix type systems will probably launch this instance in a script at boot time and detach it like any other daemon.
Here's a link to the mail archive that will help with the details and get you started:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00165.html
Here's another useful thread for the Unix folks...
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00382.html
Hope this helps, _M
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
