[EMAIL PROTECTED] (Jason Bailey) writes:
> >If the server is creating mysql.sock in and something else is looking
> >for it in /tmp, this is the easiest way to get it to work, besides
> >checking to make sure that the permissions are such that anyone who
> >needs to can read and write to mysql.sock. --
>
> I think this may be my problem in that I couldn't understand whether
> mysql.sock should be located in /var/lib/mysql but is required to be
> in /tmp. It certainly appears in /var/lib/mysql I'll try your
> suggestion for this and check permissions.
As written before, it is a permissions problem - "mysql_install_db"
(unnecesarry , don't run it - just run "service mysqld start" ) will
create files owned by root.
If you look in the default /etc/my.cnf, the database runs as user
"mysql" (for security reasons).
To fix it, do a "chown -R mysql.mysql /var/lib/mysql"
If you had started mysql the same way you start other services (httpd,
samba, etc) via tksysv/ntsysv(permanently, on every boot) or "service
httpd start" (do it right now - equivalent to "/etc/init.d/httpd
start"), it would have created the database with correct permissions
automatically. "mysql_install_db" and "safe_mysqld" aren't necesarry,
and will often cause problems.
--
Trond Eivind Glomsrød
Red Hat, Inc.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
