Re: (yet another) sock issue

2001-03-22 Thread roger westin
Sorry.. thats was realy stupid Right... it works fine now... It wasn't the permissions, it was the filename hmm. hahaha :) /roger > Because it is my.cnf, not my.cfg. > > Also they need to be world readable. > > roger westin wrote: > > > > Have the same problem, nither the ser

Re: (yet another) sock issue

2001-03-22 Thread Gerald Clark
Because it is my.cnf, not my.cfg. Also they need to be world readable. roger westin wrote: > > Have the same problem, nither the server or any client seems to read the > my.cfg files, > they are just going on the precompiled default value. > Have tried to recomplie and alot off stuff but I alwa

Re: (yet another) sock issue

2001-03-21 Thread roger westin
Have the same problem, nither the server or any client seems to read the my.cfg files, they are just going on the precompiled default value. Have tried to recomplie and alot off stuff but I always have to add the --socket /tmp/mysql.sock I got this problem after I installed the rpm clients and ad

Re: (yet another) sock issue

2001-03-21 Thread Gerald L. Clark
Charles Mégnin wrote: > > Although the my.cnf file specifies > socket = /tmp/mysql.sock > the server expects mysql.sock to reside in > /var/lib/mysql > > [mysql@localhost]$ /usr/bin/mysqladmin -u root -p password > Enter password: > /usr/bin/mysqladmin: connect to server at 'localhost'