> I am having a similar problem. I looked at another Linux machine that > has MySQL 4.0.13 running on it and the file /var/lib/mysql/mysql.sock > is there but it is empty.
Well, that's the way sockets always look to my when I look at them with a directory listing. > So I created the file, chmod to 777 Not a good idea. Instead, find out what user and group mysqld is supposed to be running as on your machine. (You might need to make them.) Then set the permissions so the mysqld daemon can get at the directory the socket is supposed to be made in, and let mysqld do its stuff. > and then > tried to light up /usr/bin/mysqld_safe and it is giving the same error > message you are getting..."Can't connect to local MySQL server through > socket '/var/lib/mysql/mysql.sock' (2)". Further examination shows > that the file I manually created was blown away after trying to light > it up. Not surprising. -- Joel Rees, programmer, Kansai Systems Group Altech Corporation (Alpsgiken), Osaka, Japan http://www.alpsgiken.co.jp -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
