https://bugs.kde.org/show_bug.cgi?id=264383
Ivan Vasin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED | --- Comment #5 from Ivan Vasin <nisavid gmail com> 2011-10-03 19:07:54 --- this issue is back. actually, i'm not sure if it was ever really gone, although my previous comment suggests that it was (sadly, without proof). the Akonadi-specific mysqld instance seems to use the right options: /usr/sbin/mysqld --defaults-file=/home/ivan/.local/share/akonadi//mysql.conf --datadir=/home/ivan/.local/share/akonadi/db_data/ --socket=/home/ivan/.local/share/akonadi/socket-ivasin-workstation/mysql.socket and the akonadiserverrc seems to point to that instance correctly: ---- [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/home/ivan/.local/share/akonadi/socket-ivasin-workstation/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true ---- however, if i do ``akonadictl restart``, it is readily apparent from the output that Akonadi still runs mysqlcheck on the db server specified in ~/.my.cnf. i can confirm this by seeing an Akonadi-specific mysqlcheck in ``ps aux``. as before, this is a bug, and it is hazardous. please fix this, so i can use ~/.my.cnf as i want (not as i want for Akonadi) without Akonadi ever touching my company's production database server. until then, i'm switching back to Akonadi + PostgreSQL. -- 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
