[Serusers] MySQL in SER 2.0

A couple of notes. 1) I've replicated my patched my_con.c file for the new SER 2.0 code. This is a patched file to work with MySQL 5.0.19+ (technically 5.0.X+, but there were problems pre 5.0.19). This is to fix problems with the timeouts that MySQL 5 has imposed on open connections. You can find the patched my_con.c file here: http://www.ideasip.com/support/utils/my_con.c.SER2 And it can be applied the same way as it's applied in SER 0.9.6. See the FAQ: http://www.iptel.org/faq/why_does_my_mysql_5_0_x_connection_time_out_when_u… 2) There are still issues with the mysql.so module compiling properly in SER when using a distro that DOESN'T have the mysql client libraries in /usr/lib/mysql Currently, the MySQL community rpms put the client libs into /usr/lib instead of /usr/lib/mysql: [root@localhost ~]# ldconfig -p | grep -i mysqlclient libmysqlclient_r.so.15 (libc6) => /usr/lib/libmysqlclient_r.so.15 libmysqlclient_r.so (libc6) => /usr/lib/libmysqlclient_r.so libmysqlclient.so.15 (libc6) => /usr/lib/libmysqlclient.so.15 libmysqlclient.so (libc6) => /usr/lib/libmysqlclient.so And for some reason, the SER makefile doesn't LOOK for them there. It will look in /usr/lib/mysql and somewhere in /usr/local/lib, but it will ignore /usr/lib. The problem is, the module compiles just fine with no errors of any kind, but when you run ser, you get the usual: module won't load, undefined symbol: log message -- which is entirely misleading. Is there any chance someone will be updating a) the my_con.c file officially (I submitted a bug back in the 0.9.6 days) for use with mysql 5 (since we've been at that stage for a while now), and b) modifying the makefile to look either in the right place or at least error out when things just aren't going to work correctly. Honestly, if I knew how to do either of these, I would... but I've looked at the makefile, and can't figure out why it's not finding the libs. Just some thoughts. For now, I just symlink the /usr/lib/libmysqlclient* files into /usr/lib/mysql and recompile the module and it works just fine. However, that seems like a less than elegant solution. N.