Re: Barnyard2 issue w/unified2 ?

[beenph <beenph () gmail com>]

On Sat, Aug 10, 2013 at 1:59 AM, waldo kitty <wkitty42 () windstream net> wrote:
> On 8/9/2013 22:53, beenph wrote:
> > I would highly suggest you that you
> > re-create a new DB with InnoDB and restart your barnyard2 sensor.
>
> why recreate??? just convert... it is a no brainer with the single command from
> mysql...

Conversion can be problematic especialy when you have data that
is corrupted.

Personally i think its better to create a new db using the new storage engine
and from there point your UI to that new db.

There is no problem to keep the old database up, for archive consulting but
i have heard a few people who had issue when using MyIASM tables
converted to InnoDB,
and when they where using native InnoDB tables there was no issue.

Can't be 100% sure but better be safe than sorry.

-elz

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=snort-users

Please visit http://blog.snort.org to stay current on all the latest Snort news!