Brian

Thanks for the reply.

I tried your suggestion, even chmod 777 mysql.sock. Still no go. I'm
starting to think it has something to do with some log files that may
have been damaged by the disk overflow last night.

I'll keep poking.

Any other suggestions most welcome.

Thanks again.


--
http://tomrue.net




On Apr 21, 5:29 pm, Brian Wakem <n...@email.com> wrote:
> tomrue wrote:
> > /tmp/mysql.sock
>
> touch /tmp/mysql.sock
>
> Will suffice.
>
> Make sure mysql has permission to enter /tmp and read/write to mysql.sock
>
> --
> Brian Wakem
> Email:http://homepage.ntlworld.com/b.wakem/myemail.png