Pete,
Thanks for the info. When you say:
>Simply running an extra instance nailed up with the persistent switch will
>have the desired effect.
Does this mean in the Global.cfg I need to reference the -persistent after the
following?
SNIFFER external nonzero "C:\IMail\Declude\Sniffer\snfrv2r2.exe -persistent
xxxcodeherexxx" 7 0
Or just download 2-3 and simply replace the sniffer.exe file (mycodebase.exe).
Sorry for the confusion, I have just seen lots of parameters within the log.
Keith
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Pete McNeil
Sent: Sat 3/20/2004 9:23 AM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [sniffer] Define Persistent sniffer.
At 07:26 AM 3/20/2004, you wrote:
>Pete,
> Nothing short of Awesome, I get it, I really get it :) One last
> question, does this change the behavior any within Declude? I am running
> the 2-2 release, in which, I saw a huge improvement in performance. Does
> this new 2-3 allow it to still be called within Declude, if so, do I
> simply call it the same way in the Global.cfg file, or are there
> additional parameters? Thanks again for the time and typing.
Sniffer 2-3 should be called the same way as 2-2 in all implementations
(Declude, mxGuard, MDaemon, Postfix, SpamAssassin, Vopmail,... others?)
There are no additional parameters **
Simply running an extra instance nailed up with the persistent switch will
have the desired effect.
_M
** Though there are no additional parameters required, we will be adding a
configuration file with version 2-3 for tuning and to support upcoming
features. We will also be adding some command line options to help
communicate with any persistent instances... They will probably be /reload,
/pause, /unpause, /stop or similar variants.
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
<<winmail.dat>>
