Sebastien Guilbaud wrote:
In addition to the other comments, if I am not mistaken, there is a
Problems section in the MySQL chapter of the manual that points you
off to the MySQL documentation on this.
This has nothing to do with you, Eric, but since we are on the subject
of MySQL timeouts: one user troubled by this problem was aserting that
Bacula remains connected at all times to the MySQL database. Nothing
could be farther from the truth (or at least the intention), unless it
is a new bug, which is unlikely because I am not experiencing this
problem on my 4.1 MySQL database.
on a couple of debian boxes, this error has been definitly ruled out by
using strictly the same version of mysql libs as the mysql server.
Which I did and still have the problem.
--
Regards,
Erik P. Olsen
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
