Thank you a lot ... I will investigate..... Regards Alberto
> -----Original Message----- > From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On Behalf > Of Pete McNeil > Sent: 07 July 2007 19:24 > To: Message Sniffer Community > Subject: [sniffer] Re: After AutoSNF MessageSniffer stops working > > Hello Alberto, > > Since you are stopping the message processing services I don't see > this causing any harm - but it does seem like overkill and may simply > help you mask another problem. > > A build up of stale job files usually indicates another more serious > problem. Normally, SNF will keep these files out of the way. The only > time it doesn't do this is when it gets killed off before it has a > chance to complete it's processing. This usually happens when some > other system event occurs or when the system is heavily overloaded for > some period. > > It would be a good idea to track down what these other factors are and > solve the root problem. > > That said, if you insist on stopping message processing at each update > I recommend that you stop processing just before the actual rulebase > swap and then restart processing after the swap and your cleanup > operations are completed. > > Note that updates are more frequent now and will become more frequent > with time. > > Note also that the next version (in testing) will not generate job > files. > > Hope this helps, > > _M > > Remainder for reference:... > > Saturday, July 7, 2007, 4:34:34 AM, you wrote: > > > Hello > > > twice (two days ago and this night) after an updating with AutoSNF, > > MessageSniffer stops working, after this accident I have found many > > files in the working directory with extensions .FIN .XXX > > > Then: > > I stop iMail SMTP Service > > I stop MXGUARD Service > > I stop MessageSniffer Service > > > I wait 30 seconds > > > I delete *.FIN > > I delete *.XXX > > I start MessageSniffer Service > > I start MXGUARD Service > > I start iMail SMTP Service > > > After that everything works fine again! > > > I had thought about adding these commands at the end of AutoSNF. (see > > below) > > What do you think about? > > > Regards > > Alberto > > > > My classic AutoSNF.cmd > > > @echo off > > > rem if there is not the trigger email message do nothing > > if NOT exist tmp*.tmp goto nevermind > > > rem AutoSNF.cmd 200208088.1419 _M > > rem > > rem 20021203 - Updated to check the download with snf2check.exe > > rem > > rem CAUTION! THERE ARE A LOT OF PLACES IN HERE TO CHANGE THE FILE > > rem NAME IF THE LICENSE ID CHANGES. BE SURE TO CATCH THEM ALL WHEN > > rem MODIFYING THIS FILE FOR OTHER SYSTEMS OR LICENSES! > > rem > > rem This file should reside in the sniffer directory along with > > rem wget. Then, this .cmd file can be scheduled in the windows > > rem scheduler... We recommend performing updates every 12 hours > > rem or so... however on most systems a daily update will be > > rem sufficient. > > rem > > rem First, get the updated rules file from the web site. > > > wget http://www.sortmonster.net/Sniffer/Updates/[codefile].snf -O > > sniffer.new --http-user=sniffer --http-passwd=thepassword > > > rem > > rem If that worked, then there will be a sniffer.new file. > > rem > > > if exist sniffer.new goto Replace > > > rem If the above test fails, then we skip to the end of the file > > rem and take no further action. Everything stays as it is. > > > goto Done > > > rem If the test didn't fail we'll replace our file. > > > :Replace > > > rem The sniffer.new file exists so we might have a good download. > > rem We'll validate it first then try to swap out as fast as possible. > > rem In order to do this as quickly as possible, we'll rename the files > > rem at the critical point. Then delete the old one next time around > > rem so that the admin has a way to recover the last rule base if needed. > > > rem The check utility gets the ID from the name but it ignores the > > rem extension so we'll rename it for the test. > > > rename sniffer.new [codefile].tst > > > rem Now we need to test the file and check our error level. If the > > rem check fails we'll skip to the end > > > snf2check.exe [codefile].tst [mySNFcode] > > > if errorlevel 1 goto Done > > > echo New File Tested GOOD! > > > rem If we didn't fail then we can go ahead and make the switch. > > > if exist [codefile].old del [codefile].old > > rename [codefile].snf [codefile].old > > rename [codefile].tst [codefile].snf > > del tmp*.tmp > > > INSERT Here the stop/start commands <------------- > > > rem Handle any additional successful system updates here (before Done). > > > :Done > > > rem If things went well we're all ok. > > rem If something went wrong then we'll do a bit of cleanup. > > > if exist [codefile].tst del [codefile].tst > > > :nevermind > > > > > > ############################################################# > > This message is sent to you because you are subscribed to > > the mailing list <sniffer@sortmonster.com>. > > To unsubscribe, E-mail to: <[EMAIL PROTECTED]> > > To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> > > To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> > > Send administrative queries to <[EMAIL PROTECTED]> > > > > -- > Pete McNeil > Chief Scientist, > Arm Research Labs, LLC. > > > ############################################################# > This message is sent to you because you are subscribed to > the mailing list <sniffer@sortmonster.com>. > To unsubscribe, E-mail to: <[EMAIL PROTECTED]> > To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> > To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> > Send administrative queries to <[EMAIL PROTECTED]> ############################################################# This message is sent to you because you are subscribed to the mailing list <sniffer@sortmonster.com>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
