On Fri, 2006-03-31 at 02:10, Heinz Ulrich Stille wrote: > Hi! > > I ran into the "MySQL server has gone away" Problem. Looks like the > culprit is mysqld's inactivity timeout. In the list archives I found > a message that the problem went away after upgrading all bacula > components to mysql 4.1. > Now I'm using 5.0 ... From the MySQL docs I gather there should be > no difference. What's up? Is somebody using bacula with version > 4 or higher and the default timeout? I'd prefer not to raise the > timeout to a couple of days (long weekend, holidays...). > Or should I create a feature request for mysql_ping()? > > MfG, Ulrich
I'm using 5.0.15 with the default time out and I haven't noticed any problems. I run 5 jobs every night except for Sunday & Monday. The last jobs run Saturday @ 6pm and then no jobs run again until Tuesday @ 6pm. Robert ------------------------------------------------------- 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
