I had the great idea yesterday to get rid of my working installation of
MySql + Midgard + PHP3 to get a real grasp of the installation in order
to write down a couple of tips for internal use in the company. I got
into a little bit of trouble with paths and libs recognization (on
RedHat 6.1), but I managed to get out alive.
Only trouble: I installed the working MySql from its RPM (latest
release) and it defaulted to putting its sock file in
/var/lib/mysql/mysql.sock.
Midgard (actually also some other PHP scripts) now fails to connect
through the local socket since it looks for it in /tmp/mysql.sock.
Symlinking doesn't look like an option (doesn't work).
Is there a way to tell either MySql or Midgard where the sock file is?
PS I used the MySql socket directive, but apparently it just managed to
get MySql angry at something and refuse to work properly (no connection
to the server whatsoever). :)
Is recompiling MySql with the --sock-file-path-directive the only way
out?
Thanks a lot guys.
--
Regards, Andrea
Andrea Resmini, architetto
Hypermedia development
OGCs.com
Corporate networking hypermedia
http://www.ogcs.com
your data, not your OS
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
