Yeah, I think my problem was just overlap, but I feel we should keep a list
of these kinds of things to look out for in the transition. For instance,
remembering to remove cron jobs that run as the 'bro' user when that user
no longer exists. We've also got systems where /usr/local/bro/logs is a
On Fri, Jul 12, 2019 at 7:15 PM Michael Dopheide wrote:
>
> Generally the idea is to be mostly backward compatible so people aren't
> forced to make any changes to external plugins, but looks like there's a
> couple small things we overlooked or had not tested that we'll want to fix
> before the
Does this branch look crazy to you at all?
https://github.com/sethhall/bro-myricom/tree/zeek-updates
My plan is to rename the whole project to zeek-myricom and set the alias
as suggested by Jon once I have some external validation that this
branch works for more people than just me. :)
I'll take a look at it.
.Seth
On 15 Jul 2019, at 12:32, Michael Dopheide wrote:
> Updating myricom to build against the install tree looks like it's
> going to
> work and will be much cleaner.
>
> -Dop
>
>
> On Mon, Jul 15, 2019 at 9:46 AM Justin Azoff
> wrote:
>
>> Speaking of that, you
>
>
> Can you give more info on how to reproduce this one? The master branch
> should currently be installing "zeek-config.h" along with a symlink to it
> named "bro-config.h", with the ideal being that people wouldn't have to
> make this change.
>
> IIRC, since we changed our default install
We just migrated to master with the name change and the afpacket plugin, so I
know the Zeek code is OK.
> On Jul 12, 2019, at 5:52 PM, Jon Siwek wrote:
>
>
>
>> On Fri, Jul 12, 2019 at 3:46 PM Michael Dopheide wrote:
>> Background: We like to run 'master', but with the name change it
On Fri, Jul 12, 2019 at 3:46 PM Michael Dopheide wrote:
> Background: We like to run 'master', but with the name change it broke
> too many things and we had to stick to 2.6.2 for the time being. Since
> then, I've started trying to convert our ansible scripts and prepare to
> make the jump.
Background: We like to run 'master', but with the name change it broke too
many things and we had to stick to 2.6.2 for the time being. Since then,
I've started trying to convert our ansible scripts and prepare to make the
jump. Today I discovered the bro-myricom package would fail to build.
