https://bugs.kde.org/show_bug.cgi?id=274750
--- Comment #8 from Francesco Riosa <francesco+kde pnpitalia it> 2011-07-21 21:13:34 --- (In reply to comment #7) > well, yes, using an external mysql instance supposes that you configure your > mysql server first. Akonadi cannot do that for external servers for obvious > reasons. > > You can find the special settings used when Akonadi starts its own mysql > instance there: >https://projects.kde.org/projects/kdesupport/akonadi/repository/revisions/master/entry/server/src/storage/mysql-global.conf Thank you for discussing and showing the Akonadi default configuration, I see the only ones that are _really_ required are ATM max_allowed_packet=32M wait_timeout=1296000 with possibly the addition of max_connections=256 the others are there just for performance reasons or can be set from the client disclaimer, I'm versus any kde-sc starting whatever database server, because IMHO it's a bad thing (I'm trying to convince DigiKam developers to don't do that too), so possibly the following is a bit of a rant but there are also suggestions, so I'll keep writing. Setting the timeout to 15 days is just try to hide the problem, there are multiple reasons that can bring a database connection down, clients must simply be resilient to that. Developers should test with timeouts no longer than 60 seconds. A desktop environment should not try to start a database, sqlite is the one that does embedding well. For their inherent complexity database servers should be started by the same scripts that start kdm, distributions have the expertise to do that and you (kde) should simply impose them a minimum. simply akonadi at startup should test a minimal safe values for a restricted number of variables (which don't include timeouts imho) then if the database server is down or does not meet the requirements it should warn the user. Thanks for reading (if you reached this ;) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
