On Tuesday, May 10, 2005, 12:41:42 PM, Matt wrote: M> Warning!
M> When you add a RulePanic entry and are running Sniffer in persistent M> mode, you have to restart the service for it to take effect. You can also issue "<license>.exe reload" <snip/> M> Pete, when you send out these notifications, would you please add a M> few instructions to them, including the file name that needs to be M> modified, i.e. <RuleBaseID>.cfg, the format of the line, and the M> instructions to restart the service. Those are good ideas --- this is so rare that I'm making up the procedure on the fly and I skipped those parts. I've posted another message with these details. M> Another important piece of M> information would be the time that the bad rule was created, M> otherwise we need to search our logs for it. My first hit on this M> was yesterday at 9 p.m. EST, but some probably hit it earlier by up M> to a couple of hours I would imagine. I will hunt that down shortly. _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
