Hi Pete,
I'm running a Sniffer service on a secondary system so that I can test my rulebase update script. After I changed to "curl" (to maintain the server timestamps), I'm now seeing the following in the status.minute.log: <rulebase utc="20081008183610" /> <active utc="20081008183610" /> <update ready="no" utc="20081008143610" /> The "update ready" note matches the timestamp of 2:36 PM of actual rulebase SNF file. Which is correct, because when it downloaded from your server at 11:35 AM EDT, your server presented this HTTP header: Date: Wed, 08 Oct 2008 15:33:44 GMT Server: Apache/2.0.46 (Red Hat) Last-Modified: Wed, 08 Oct 2008 14:36:10 GMT ETag: "3ec4df2-cb96c0-458bed6588a80" Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Transfer-Encoding: chunked Content-Type: application/x-sortmonster But, how is the rulebase and active UTC determined? Where is this "18:36:10" coming from. It seems to me as if somehow Sniffer adjusted the (already) GMT time of 14:36 by yet ANOTHER 4 hours, giving it a fantasy timestamp of 18:36. The net effect appears to be that my test machine doesn't get an "UpdateReady.txt" until 4 hours have passed. My improved getRulebase.cmd works perfectly, but it will only get launched every four hours, at best. Best Regards, Andy
