Uhm, yeah, Debian/Ubuntu have had the MySQL socket there for ages. Any
packaged application looking for it in the wrong place should be fixed.
Any non-packaged app is being installed/run by someone who knows what
they're doing (in theory) and can specify the socket location manually.
--
Mysql so
On Wed, May 14, 2008 at 05:37:13PM -, Stephan Hermann wrote:
> I think it's more a bug in the perl/php stuff then in mysql.
> The socket file should sit in /var/run/mysqld and not in /tmp/
> More detail:
> We should fix the packages which are looking for the socket file in /tmp then
> symlin
TBH,
I think it's more a bug in the perl/php stuff then in mysql.
The socket file should sit in /var/run/mysqld and not in /tmp/
More detail:
We should fix the packages which are looking for the socket file in /tmp then
symlinking the socket file to /tmp.
It's a good workaround for the time now,
** Description changed:
Binary package hint: mysql-server-5.0
Many projects using (perl) DBI and (php) adodb database APIs are looking
for the mysql socket file in /tmp/mysql.sock rather than
/var/run/mysqld/mysqld.sock.
Changing the .cnf file to return the sock file to /tmp may ca
** Attachment added: "mysql.patch"
http://launchpadlibrarian.net/14518692/mysql.patch
--
Mysql socket file breaks PHP/Perl/etc...
https://bugs.launchpad.net/bugs/230393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
