I'm using Bro to crunch a whole lot of pcap files, so I want to run a bunch of instances in parallel, but I'm worried that they will trip over each other accessing the persistent state file (.state/state.bst
). Is there any way to tell Bro that it should neither read nor write any persistent state, no matter what the scripts might want? I cannot find anything relevant in the manual. Making .state
an inaccessible directory has the desired effect, except that (reasonably enough) Bro issues a warning about not being able to get in there, which I would prefer to avoid (I'd have to filter it out at a higher level).
问问题
72 次