[ts-gen] MySql 5.1.37 configuration on Fedora System

[R P Herrold]

On Mon, 7 Dec 2009, Billy Pilgrim wrote:

> I still am unable to configure mysql on Fedora 11 or Fedora 12 so the shim
> is happy. I had this problem the last time I tried it out using Fedora 7 and
> mysql 4x but got it going with some simple changes to my.cnf. Problem exists
> on both 64 and 32 bit version of Fedora 11 or 12 and mysql 5.1.37.
> 
> I have scoured the posts and the documentation and have yet to find a
> solution to this problem. If anyone has the shim running on Fedora 11 or 12
> please post your mysql configuration.

As a matter of diagnostic technique, it might may sense to 
start with a clean slate, and make a copy of the initial (as 
deployed) configuration file, and then minimal changes, one at 
a time, to permit using 'diff' to see just the changed parts.

[herrold at xps400 ~]$ cd /etc
[herrold at xps400 etc]$ ls my*
my.cnf  my.cnf-OLD  my.cnf.rpmnew
[herrold at xps400 etc]$ diff -u my.cnf-OLD my.cnf
--- my.cnf-OLD  2007-04-20 16:05:07.000000000 -0400
+++ my.cnf      2007-04-20 16:05:31.000000000 -0400
@@ -9,6 +9,10 @@
  user=mysql
  basedir=/var/lib

+[mysqld]
+transaction-isolation = SERIALIZABLE
+
+
  [mysqld_safe]
  log-error=/var/log/mysqld.log
  pid-file=/var/run/mysqld/mysqld.pid
[herrold at xps400 etc]$

That should be the only needed change.   Remember the 
mysql-server needs to be restarted before this takes effect.


We check for the four ACID aspects needed being present at 
connect time and emit a diagnotsic and die (as I recall) if 
not met.  There was a brief issue upstream at MySQL AB as to 
the autoincrement not behaving properly, but not on the Red 
Hat family Fedora distribution variants

To make sure, I re-loaded my testing database from scratch 
after a drop, and nothing neems to have changed here (but on a 
CentOS 5 platform.)  I have a VM with a Fedora RawHide in it, 
and will see there

-- Russ herrold