List:General Discussion« Previous MessageNext Message »
From:Gerald Clark Date:March 22 2001 1:47pm
Subject:Re: (yet another) sock issue
View as plain text  
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 always have to add
> the --socket /tmp/mysql.sock
> 
> I got this problem after I installed the rpm clients and added the server by
> compiling an installing it. So ...
> Why isn't the rpm and installation source putting mysql in the same
> directory and have the same defaults.
> And how do you actualy make it read the my.cfg file? (shouldtn't it be read
> atomaticly?)
> 
> /roger
> 
> ----- Original Message -----
> From: "Charles Mégnin" <charly@stripped>
> To: "MYSQL" <mysql@stripped>
> Sent: Wednesday, March 21, 2001 9:24 AM
> Subject: (yet another) sock issue
> 
> > 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' failed
> > error: 'Can't connect to local MySQL server through socket
> > '/var/lib/mysql/mysql.sock' (111)'
> > Check that mysqld is running and that the socket:
> > '/var/lib/mysql/mysql.sock' exists!
> >
> > Any thoughts ?
> >
> > ---------------------------------------------------------------------
>
Thread
(yet another) sock issueCharles M├ęgnin21 Mar
  • Re: (yet another) sock issueGerald L. Clark21 Mar
  • Re: (yet another) sock issueroger westin21 Mar
  • Re: (yet another) sock issueGerald Clark22 Mar
  • Re: (yet another) sock issueroger westin22 Mar