Sorry about the late reply. The error is actually 'pebcac' in nature. The
scripts that I had been editing weren't placed back into the default policy
path, which is why no matter the change , the same result occurred. Perhaps
something that could be attributed to a lack of coffee in the early
morning. Sorry guys :)
All is still well in the world of bro scripts.
On Fri, Dec 16, 2011 at 11:43 AM, Siwek, Jonathan Luke
Internal values can be set as arguments,
Ex. bro -Cr somefile.trace some/policy/here myvar=somevalue
as well as at the script level,
Ex. redef myvar = somevalue;
For variables declared with the &redef attribute, yes.
It seems I cannot get the script level value to
set, but the command
line argument is correctly set.
It should work both ways. Is there a specific error you're getting or a
specific/contrived example you can give?