[sniffer] Re: New IMPROVED getRulebase.cmd script

2009-03-11 Thread Bonno Bloksma
Hi,

First one comment about the script.
Just before the CLEANUP label the lck file is deleted. Right after that it is 
deleted again in the CLEANUP section.
The first can savely be removed.

Second,
Why does this problem start just now with a DST shift somewhere? I'n nowhere 
near your timezone (GMT+1 or +2) so should there not have been a problem long 
before where my system would see older files at your system several times a day 
when in fact there would be a newer one? Does that mean my system has been 
getting only two or three updates a day where it should have gotten over a 
dozen?
Unfortunately I disabled logging a while ago when everything seemed to run 
smoothly. :-(

Someone to your west would have seen a new rulebase every time they checked no 
matter what DST.
Or is it just that you finally noticed it due to the DST shift?

Met vriendelijke groet,
Bonno Bloksma
senior systeembeheerder

tio 

hogeschool hospitality en toerisme 
begijnenhof 8-12 / 5611 el eindhoven
t 040 296 28 28 / f 040 237 35 20

b.blok...@tio.nl  / www.tio.nl 


- Original Message - 
  From: Pete McNeil 
  To: Message Sniffer Community 
  Sent: Tuesday, March 10, 2009 2:40 PM
  Subject: [sniffer] New IMPROVED getRulebase.cmd script


  Hello Sniffer Folks,

  At the following link you will find a zip file containing the open 
  source CURL utility and an updated version of the new getRulebase.cmd 
  script. The old getRulebase.zip file has been replaced with the new one 
  in the same location (you may want to clear your browser cache if you 
  downloaded the previous version):

  http://www.armresearch.com/message-sniffer/download/CURL-getRulebase.zip

  The new getRulebase.cmd script produces a getRulebase.txt file each time 
  it is run so that you can see what happened.

  No errors are reported to the screen. If there are errors they will show 
  up in the getRulebase.txt file.

  There is a comment at the bottom of the script where you can add a line 
  to email the getRulebase.txt file to yourself if you want to have the 
  script inform you each time it runs.

  _M


  #
  This message is sent to you because you are subscribed to
the mailing list sniffer@sortmonster.com.
  To unsubscribe, E-mail to: sniffer-...@sortmonster.com
  To switch to the DIGEST mode, E-mail to sniffer-dig...@sortmonster.com
  To switch to the INDEX mode, E-mail to sniffer-in...@sortmonster.com
  Send administrative queries to  sniffer-requ...@sortmonster.com



[sniffer] Re: New IMPROVED getRulebase.cmd script

2009-03-11 Thread Pete McNeil

Bonno Bloksma wrote:
Why does this problem start just now with a DST shift somewhere? I'n 
nowhere near your timezone (GMT+1 or +2) so should there not have been 
a problem long before where my system would see older files at your 
system several times a day when in fact there would be a newer one? 
Does that mean my system has been getting only two or three updates a 
day where it should have gotten over a dozen?
Unfortunately I disabled logging a while ago when everything seemed to 
run smoothly. :-(
 
Someone to your west would have seen a new rulebase every time they 
checked no matter what DST.

Or is it just that you finally noticed it due to the DST shift?


The reason DST is an issue is because the previous wget based script 
stamps the downloaded rulebase with the local clock instead of the 
timestamp that came with the file from the delivery server. As a result 
the timestamps might not agree.


The recent change in the start of DST in the US is not reflected 
everywhere AND some locations use different DST start dates. The result 
of this is that when using the old script the local timestamp created 
using the local clock is likely to be behind the delivery server's 
timestamp by an hour.


The new update-script mechanism in SNFServer compares the local file's 
timestamp to the timestamp reported by the delivery server once every 
minute.


When the local timestamp is used and the local time is behind the clock 
on the delivery server then the freshly downloaded rulebase file 
_appears_ to be an hour old and this does not change no matter how many 
times the file is downloaded.


Before DST the local clock and the delivery server's clock would 
generally agree and so there was no problem.


Hope this helps,

_M



[sniffer] Re: New IMPROVED getRulebase.cmd script

2009-03-11 Thread MxUptime.com
Pete

 

Have you considered using Rsync as the delivery mechanism for the downloads
instead of CURL/WGET?