My exim runs with a MySQL Backend.

I upgraded MySQL from the 4.0 branch to the 4.1 branch today

i also updated the MySQL clients and such as well

bad mistake, all my mail went offline when doing this.

when i typed "exim" in console, it complained about libmysqlclient.so.12 is missing.

when looking in the mysql lib dir, its now called libmysqlclient.14

looks like its gone up a version

anyway, i thought i could cheat and link libmysqlclient.so.12 to libmysqlclient.14

i then typed "exim" into my console, this time, the binary run fine and displayed this:

Exim is a Mail Transfer Agent. It is normally called by Mail User Agents,
not directly from a shell command line. Options and/or arguments control
what it does when called. For a list of options, see the Exim documentation.

which is correct. But then this started to appear in my exim panic log:

2004-12-18 01:27:20 queue run: process 5140 crashed with signal 11 while delivering 1CfT6k-0003Ng-Ie
2004-12-18 01:27:20 queue run: process 5142 crashed with signal 11 while delivering 1CfT1u-0003MY-Em
2004-12-18 01:27:20 queue run: process 5144 crashed with signal 11 while delivering 1CfSsE-0003B5-73
2004-12-18 01:27:20 queue run: process 5146 crashed with signal 11 while delivering 1CfSol-00038c-Kt
2004-12-18 01:27:21 queue run: process 5157 crashed with signal 11 while delivering 1CfSYs-0002xf-Nm
2004-12-18 01:27:22 queue run: process 5507 crashed with signal 11 while delivering 1CfSqj-00039D-Jp
2004-12-18 01:27:22 queue run: process 5509 crashed with signal 11 while delivering 1CfSsU-0003BD-M7
2004-12-18 01:27:22 queue run: process 5511 crashed with signal 11 while delivering 1CfSx4-0003KU-BK
2004-12-18 01:27:23 queue run: process 5513 crashed with signal 11 while delivering 1CfSx4-0003KV-Bd
2004-12-18 01:27:23 queue run: process 5515 crashed with signal 11 while delivering 1CfTLG-0008Nq-UI

Compiling exim again will fix this no doubt, but then i also have to compile and patch my qpopper for mysql as well, which is a pain in the *** to be honist.

So my question is..... is there anyway to statically compile exim with the mysql libs so that next time i upgrade to the next major version of mysql it doesn't go nuts.

Thanx

as i recall, i didn't have problems when i did the symlink cheat on FreeBSD.

on my Debian system, i have libmysqlclient10 and 12 installed alongside with 14. perhaps you could try that out (assuming the server is backwards compatible with the older client libraries, which has been the case for me so far).

Yea server is backwards compatable because my php is still using the built in clients which is 3.x

From now on i think i will keep the old clients on the system when i upgrade

tried to compile exim with the new .14 version of the mysql client..... its not happy, it wont compile

dont think exim works with it yet, so i am using the mysql 4.0.22 client with it at the moment, and its working ok