On Fri, Jan 11, 2008 at 09:48:33AM +0900, Jim Barber wrote:
> Is it possible to have the package check the vseq number in the schema
> table and then automatically perform the upgrade? Fixing this problem
> involved a lot of mucking around since the information required was not in
> any of the REA
I also just encountered this problem.
I tried the above steps described by Javier and hit the following problems.
I tried to do these updates by logging into MySQL using the snort user.
It didn't have the privileges to run the SQL commands described.
So I looked at my /etc/mysql/debian.cnf file t
On January 4, 2008, Javier Fernández-Sanguino Peña wrote:
> tag 445334 upstream
> thanks
>
> On Thu, Oct 04, 2007 at 08:13:12PM -0600, Gordon Haverland
wrote:
> > I've gone through 2 snort-mysql upgrades now, and seen in my
> > logs after the upgrade a note that my dbase version (106) is
> > too o
tag 445334 upstream
thanks
On Thu, Oct 04, 2007 at 08:13:12PM -0600, Gordon Haverland wrote:
> I've gone through 2 snort-mysql upgrades now, and seen in my logs after
> the upgrade a note that my dbase version (106) is too old, I need to
> have 107 (or better). The log notes that there are "cur
Package: snort-mysql
Version: 2.7.0-6
Severity: normal
I've gone through 2 snort-mysql upgrades now, and seen in my logs after
the upgrade a note that my dbase version (106) is too old, I need to
have 107 (or better). The log notes that there are "cursory details" in
README.database. Well, if
5 matches
Mail list logo
