liviu,
At last, I get your name right, if a little under-capitalised. Your
help was the first step in maybe a dozen or so that got the site back
up. So thank you kindly for that. Just some minor linking to outside
the chroot and it'll be perfect.
But thanks for the help.
guy
On 19/08/2013 02:54, Liviu Daia wrote:
On 18 August 2013, Guy Ferguson <guyfergu...@tpg.com.au> wrote:
Livia,
If you want to address me by name, s/Livia/Liviu/ please. It might
not be much, but it's my name, and I kind of became attached to it over
the years. :)
Thanks for your help.
I modded the /etc/my.cnf to add in the extra "/run" directory.
A few other tweaks here and there and i can now get a test.php to
connect to the
default host mysql ($conn=mysql_connect...)
So now i'm confident that mysql is working and connectable...I just
ahve to sort out why drupal is
unhappy, which no doubt is a chroot issue.
[...]
Like I said, the easy solution to that is to use TCP connections.
As others have pointed out, just set hostname to 127.0.0.1 in your
Drupal config, and you should be fine.
If you insist on using UNIX sockets, you probably want to set
socket = /var/www/run/mysql.sock
in the /etc/my.cnf, then copy /etc/my.cnf to /var/www/etc/my.cnf, and
set
socket = /run/mysql.sock
in the client section in /var/www/etc/my.cnf. There is no advantage in
doing things like this though, you'd be just looking for future trouble.
Regards,
Liviu Daia
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3392 / Virus Database: 3211/6584 - Release Date: 08/16/13
