Well, PHP gets that path from the mysql client library, so if it isn't
getting the right one then your client library is wrong. Check it:
strings /usr/lib/libmysqlclient.so | grep sock
Mine outputs:
/var/lib/mysql/mysql.sock
-Rasmus
On Sat, 22 Sep 2001, Ashley M. Kirchner wrote:
> Rasmus Lerdorf wrote:
>
> > PHP hasn't hardwired anything. The MySQL library which ships with PHP
> > does have this hardwired, but that is why I told your to use
> > --with-mysql=/path which tells PHP to not use the built-in library and to
> > use the system one which has the correct socket location built in.
>
> I did. --with-mysql=/usr/local still says the socket is in /tmp/mysql.sock
> when it's not. It's in /usr/local/var/mysql/mysql.sock. mySQL is running fine,
> and the socket is _not_ in /tmp/mysql.sock. So why does PHP insist on it being
> there?
>
> --
> W | I haven't lost my mind; it's backed up on tape somewhere.
> +--------------------------------------------------------------------
> Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
> IT Director / SysAdmin / WebSmith . 800.441.3873 x130
> Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
> http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
>
>
>
>
--
PHP Install Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
