I've been a fool. I didn't realize that I had to use the following option when starting up the mysql daemon:
--socket=/usr/local/mysql/run/mysql_socket I suppose that my instructions might have left this out. Normally the socket is created in /tmp (absolute pathname) right? But when I specified --with-unix-socket-path=/usr/local/mysql/run/mysql_socket in the ./configure , I assumed that this would automatically set the socket to occur in /usr/local/mysql/run without any further work on my part. So does that mean that forevermore when invoking the daemon I need to use the socket option? -- Erik PS: the documentation at mysql.com is incredible. --- Bill Adams <[EMAIL PROTECTED]> wrote: > Erik Price wrote: > for > > some reason I assumed that the socket would be created dynamically > when > > I started the mysql daemon. > > It does. > > Try chown mysql:mysql /usr/local/mysql/run > > Then restart mysqld. > > b. > ===== -- Is this where you really wanted to go today ? -- http://www.redhat.com/about/opinions/xp.html __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com --------------------------------------------------------------------- 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
