FQuest Upgrade: MySQL Daemon

[Terra]

As promised, all MySQL engines have been updated to:
3.23.39

From the current changelog, I did not feel compelled to wait until '3.23.40' was released...

From an earlier request, I have implemented better clock synchronization controls on the MySQL engines that should help keep Server<->MySQL skew to a minimum...

Enjoy... :)

--
Terra
--What, me worry?!?--
FutureQuest

[Bradley]

W00T! you rock TeRRa :P

[Rich]

Not sure where these modules stand across all servers. A few months ago the latest modules were installed on SIX, based on a request I made.

You might want to consider the latest DBD and DBI::mysql modules for upgrade on all servers since these modules tend to enable the latest mysql capabilities.

Rich

[Terra]

All upgrades/changes across TAZ through ASTRO are frozen for the time being, as whatever changes I make now will become moot shortly...

The existing DBI::DBD drivers will suffice in the interim, unless it can be shown that there are major compelling reasons to do so...

--
Terra
--Vanilla Ice--
FutureQuest

[jr]

Just a minor note: It appears the MySQL client tools in /usr/local/mysql/bin were not updated (at least on DEEDEE). They're still at version 3.23.32.

[Terra]

In order to maintain least amount of impact on the Community Servers, the MySQL command line tools, includes, libs are not updated unless absolutely necessary...

This is one of many reasons I split off the MySQL daemons to backside engines, and MySQL has been pretty darn good at ensuring the 'clients' and 'engine' work well together no matter which version...

In other words, the version mismatch is not going to affect you much (if any) at all... If you can show me otherwise, then I will sync up the CS<->MySQL version...

What I will most likely do is update the MySQL client/libs when I release a new PHP version, that seems to be the most logical way to maintain updates...

--
Terra
sysAdmin
FutureQuest