I want to test our memcmp() binaries to see if we have the mysql binaries that
are impacted by the recent security breach. How do I test it?
Thanks
Life was meant to be mobile
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com
You can specify installation directory when you run the installer script
instead of make. Also update the MySQL base and data directories in the
mysql.server file under the support files directory. You can copy that file to
/etc/init.d and add MySQL to chkconfig
Sabika
Life was meant to be mob
Use replication as your fail over and why not percona's xtrabackup or lvm type
backup if you need a backup?
Sabika
On Feb 19, 2013, at 1:20 PM, Reindl Harald wrote:
> surely
>
> * use "mysql_upgrade -u root -p" after EACH update
> * upgrade regulary
>
> we went from MySQL 3.x to 5.5.30 unt
I would from 5.1.40 to 5.5.8 first and then to 5.6
On Dec 4, 2013, at 11:33 AM, Ilya Kazakevich wrote:
> Hello,
>
> Have anybody tried to upgrade 5.1 to 5.6? I believe running mysql_upgrade
> should be enough, but does there are some caveats?
>
> Ilya Kazakevich.
--
MySQL General Mailing Li