MySQL Schema update from 106 to 107

[Ian Masters <ian () acces co jp>]

Hi again,

I've found some fixes to the db schema errors which updating from snort
v2.3.2 to v2.8.3.1. It seems I have to run the following commands in mysql:
1. # ALTER TABLE signature ADD sig_gid INT UNSIGNED;
2. # INSERT INTO schema (vseq, ctime) VALUES ('107', now());
3. # DELETE FROM schema where vseq='106';

I hope that's right.

What I want to know is, if I do this, will my v2.3.2 snort installations
be able to send alerts to the DB with schema 107 *before* I upgrade them?

If not it seems I'm in a kind of chicken and egg situation. I'll have to
get everything upgraded at the same time.

Thanks

Ian

-- 
Snort v2.3.2 on various *nix; ACID v0.9.6b23


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
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://www.geocrawler.com/redir-sf.php3?list=snort-users