Re: Harcoded mysql.sock path in mysqlnd extension
| From: | Remi Collet | Date: | Mon, 16 Jan 2012 18:04:38 +0000 |
| Subject: | Re: Harcoded mysql.sock path in mysqlnd extension | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-57380@lists.php.net to get a copy of this message | ||
Le 16/01/2012 18:39, Ulf Wendel a écrit :
> Am 16.01.2012 11:19, schrieb Remi Collet:
>> P.S. well, don't know if having such a hardcoded path is a good idea....
>
> mysqlnd is a libmysql drop-in replacement. Guess what libmysql does... -
> do "strings libmysqlclient.so | grep mysql.sock" on a standard source
> build.
$ strings /usr/lib64/mysql/libmysqlclient.so.18 | grep mysql.sock
/var/lib/mysql/mysql.sock
Which is taken from configure option
--with-unix-socket-path=/var/lib/mysql/mysql.sock
Default (cmake config) is /tmp/mysql.sock, but even upstream package
don't use it and set it to %{mysqldatadir}/mysql.sock
I'm ok with the hardcoded default value of /tmp/mysql.sock.
I just don't understand why mysqlnd doesn't honour config option (even
if this value will probably be never used)
Regards,
Remi.