Dear Kern, in message <[EMAIL PROTECTED]> you wrote: > > In looking at Debian, I find for me personally I wouldn't want to run on > "stable" as it is too old. I don't really need that much stability. > "testing" is not my piece of cake either (at the moment) because it doesn't > have timely security updates (though this appears to be changing). Who knows > perhaps SuSE is a reasonable contender.
Don't spend effort on trying SuSE, please. You have got better things to do. Or at least better ways to waste your time. > If users are having this "MySQL went away" problem on MySQL 4, no one has > explicitly said so, and in that case then it is a lot less clear what is > going on. I never had any such problems under FC4 and before (mysql-4.1.16-1.FC4.1); this was new to me under FC5, and as far as I can tell from asingle 24 hours cycle I can say that increasing "wait_timeout" to more than the pause between bacula runs really solved the problem. What I don't understand is why mysql would time out if no connection is open - and I definitely didn't have any jobs running at the time of the error messages. It's enough to wait long enough in idle state and then type a "list volumes" or any other command accessing the database in the console. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] If I had to live my life again, I'd make the same mistakes, only sooner. -- Tallulah Bankhead ------------------------------------------------------- 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&kid0944&bid$1720&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
