Posted by Peter H. Coffin on 12/27/05 18:36

On Tue, 27 Dec 2005 11:46:33 +0100, Schraalhans Keukenmeester wrote:
> Ben wrote:
>> I installed mysql 5.0 on redhat 9.0 from source (tar).
>> The whole procedure occured properly, i could do ./mysqld_safe.
>> But when i want to start the client: mysql, i get :error 2002: cannot
>> connect to mysql server through 'tmp/mysql.sock'.
>>
>> I set /tmp with the sticky bit, because otherwise file 'mysql.sock' woukd be
>> deleted !?.
>> I also created 'my.cnp into /etc, but my problem is that there is no file
>> 'mysql.sock'.
[..]
>>
> I am not sure, but would setting the sticky bit not prevent mysqld from
> creating a new socket every time it is started ? I don't see the reason
> for the stick bit here. And I noticed you talk about /tmp and the error
> speaks of tmp. Could that be tmp relative to the mysql path perhaps ???

The bit prevents *other* user IDs from deleting the socket. If user
'mysql' creates and owns /tmp/mysql.sock, then only mysql and superuser
(e.g. root) can delete the file, regardless of write permissions on the
mysql.sock file.

But, as has been pointed out elsewhere in the thread, that's not the
problem. The problem is that the daemon isn't starting.

--
_ o
|/)

[Back to original message]