Version: (using Devel) OS: Linux Installed from: Compiled sources Since some systems use network file systems (that do not support Unix Domain Sockets) for home directories, it should be possible to put the mysql.socket file somewhere else by a configure option like already possible for the akonadi server socket.
any progress here?
Hi, I would really appreciate a soon fix (imho it should not be so hard do change a path/add a line in a config file or am I wrong?). Since KDE SC 4 is getting into more and more distributions, I currently see this problem at large university networks (OpenSuse, Debian Testing). Another bad side effect: when the socket cannot be created, the standard MySQL log file size is 64 MB large. This logfile is created two times, which are 128 MB for a not working Akonadi server. Inside a usual quite small user's home this is much too big. At least this triggered problem can be repaired by mysql-config files...
Actually i don't consider this as a quite severe blocker. At least it blocks me from rolling out kde4. kde allready handles that by creating a dir in /tmp and a link to it ( ~.kde/socket-<hostname> ) - why not use that?
I shouldn't type when not awake. What i wanted to say: "I don't consider this as a Wish, i consider this as quite severe blocker" I also found bug 179006 and bug 182292 which are marked fixed, but without mentioning a fix. So if there has been a fix, could please someone state a version or revision? At least current version from debian squeeze ( kde 4.4.5, akonadi-server 1.3.1-3+b1 ) resists all my efforts to start.
This is not necessary IMHO, see bug 179006, which I just reopened: it could just work out of the box if using a symlink where necessary.
Hej, both, Akonadi and MySQL store their sockets in a directory $TMP/akonadi-<username>.<random> now, which is symlinked to $HOME/.share/akonadi/sockets-<hostname>. So no further manual configuration is needed anymore. Ciao, Tobias