Ed,
Once again, thanks for the email response. I'm going to try all the suggestions I've
received.
A colleague has suggested as I'm new to Linux to select the 'Install Everything'
option in red hat 7.1. He suggests that it's probably easier (for me) to get everything
installed and work backward (uninstall the unnecessary) as I learn more.
>If the server is creating mysql.sock in and something else is looking for it in
>/tmp, this is the easiest way to get it to
>work, besides checking to make sure
>that the permissions are such that anyone who needs to can read and write to
>mysql.sock. --
I think this may be my problem in that I couldn't understand whether mysql.sock
should be located in /var/lib/mysql but is required to be in /tmp. It certainly
appears in
/var/lib/mysql
I'll try your suggestion for this and check permissions.
> Well, it wasn't a pun :) Details are critically important, especially when you work
>with complex systems like these. I was commenting on the lack of detail in your post
>-
My mistake about the Pun. I do agree details are important; I will use mysqlbug next
time, if I get no joy. I'd found several, if not more, postings from several people
with
the same type of question, regarding the error I was getting. I'd assumed that this
common problem was well understood and didn't require explicit detail from myself.
> you ran "something" and "something" happened, but you weren't quite sure what. It's
>much more difficult when people have to guess what you did. I'm not trying to flame
>you
> at all - but you will probably be able to get a lot more, and a lot higher quality,
>help if you can supply as much detail as possible.
I would'nt blame you for flaming my first email was a little rude. The detail I will
try for next time.
>> > I've deleted it and running something above has brought it back again!- this
>> > is good I think
>>
>> >> Bad idea.
>>
>> Slightly sarcastic- sorry
>
> No, this really *is* a bad idea! The mysql.sock file is created by the server - if
>you delete it, you will not be able to connect locally.
I'd been sarcastic and was apologising. I realised it was a bad idea but was getting
frustrated and wanted to see if it would be recreated as a test if I was running the
server at all. On deleting it I was finding that it was being recreated when running
"something".
Something- I wasn't sure about at the time either mysql_install_db or safe_mysqld & -
still not sure but will check tonight when I get home.
Dr Jason Bailey
Desktop Applications Consultant
Computing Service
The University of Sussex
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
