Pete,
I upgraded to the latest getRulebase file and followed the instructions, but
now all I see on my windows system (DST) is the following: (I replaced my
license ID # with )
snf2check: .new ERROR_RULE_FILE!
1 file(s) copied.R:2349772 [0/12 - 0] W:0 C:0 B:0 T:0 S:0
sn
Hello Sniffer Folks,
DST Update Problem: A bug in the old getRulebase.cmd script caused Win*
systems to discard the server's timestamp on rulebase files and
substitute the local timestamp. As a result any system that change to
DST (daylight savings time) after our rulebase delivery servers wou
Serge wrote:
Hello Pete
We use our own wget batch file, rather long and complicated, do all
the following (and more)
uses gzip
only download if the server file is newer
uses lock file
test if lock too old (>60') and eventualy deletes it (in case of a
reboot before deleting the lock, for exam
Hello Pete
We use our own wget batch file, rather long and complicated, do all the
following (and more)
uses gzip
only download if the server file is newer
uses lock file
test if lock too old (>60') and eventualy deletes it (in case of a reboot
before deleting the lock, for example)
retry dow
Richard Stupek wrote:
If we have a up to date snf file, will the script cause snf2check to
print out "ERROR_RULE_FILE!"?
Yes. It may. If the current .snf file is up to date then CURL will not
download the .new file and snf2check will not find it.
_M
###
If we have a up to date snf file, will the script cause snf2check to print
out "ERROR_RULE_FILE!"?
On Mon, Mar 9, 2009 at 11:16 AM, Pete McNeil
wrote:
> Hello Sniffer Folks,
>
> We have determined that using the latest getRulbase.cmd script w/ CURL does
> resolve the DST problem.
> Please update
Andy Schmidt wrote:
Hm - seems that I may have commented out WGET and have been using CURL even
with the new version (because of date mismatches).
So - maybe the enclosed will help.
It SEEMS as if my /rulebase/ folder has been updated at least twice since
8:30 AM this morning...
That may be
Hello Sniffer Folks,
We have determined that using the latest getRulbase.cmd script w/ CURL
does resolve the DST problem.
Please update your getRulebase.cmd script as soon as possible.
You can find the latest getRulebase.cmd script and a copy of CURL here:
http://www.armresearch.com/message-s
Hm - seems that I may have commented out WGET and have been using CURL even
with the new version (because of date mismatches).
So - maybe the enclosed will help.
It SEEMS as if my /rulebase/ folder has been updated at least twice since
8:30 AM this morning...
-Original Message-
From: Mes
Yes, with the OLD version (before the upgrade) I used to run my own script -
and it successfully used:
curl http://www.sortmonster.net/Sniffer/Updates/MyRuleBase.snf -o
MyRuleBase.snf.gz -s -S -R -z MyRuleBase.snf -H "Accept-Encoding:gzip" -u
sniffer-userid:sniffer-pwd
if exist nwb655oh.snf.gz
Hello Sniffer Folks,
IMPORTANT!
We have discovered a problem with the rulebase update mechanism that is
currently installed on most systems; and this problem combined with
daylight savings time is causing trouble with rulebase updates.
There has long been a bug in the getRulebase script usin
11 matches
Mail list logo
