Thank you for your answer.
Here is what I did
cd
/seqweb/mysqlhome
mercure{mysql}140: more .my.cnf
# The following options will be passed to all MySQL clients
[client]
user = mysql
password = xxxx
port = 3306
socket = /tmp/mysql4.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
[mysqldump]
[mysql]
[isamchk]
[myisamchk]
[mysqlhotcopy]
I still have the problem.
DBI connect('database=mysql;host=localhost;port=3306','mysql',...) failed:
Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) at
/seqweb/mysql4/myscripts/4/check_innodb.pl line 62
Also this is a less attractive solution since the same user will work on
version4 and version 5.
Thank you
-----Message d'origine-----
De : Gerald L. Clark [mailto:[EMAIL PROTECTED]
Envoyé : Tuesday, 12 September 2006 10:39
À : Duhaime Johanne
Cc : [email protected]
Objet : Re: 2 versions of mysql on Unix: problem with the socket
Duhaime Johanne wrote:
> I am running mysql 4.1.7 on solaris 9. I want to install 2 versions (versions
> 4.1.7 and 5) on the server. I am reconfiguring my scripts in that
> perspective.
>
> I have a script that start the mysql v4 so that I finally have:
>
> 7002 pts/4 S 0:00 /bin/sh /seqweb/mysql4/bin/mysqld_safe
> --defaults-file=/seqweb/mysqldata/my.cnf --port=3306
> --socket=/tmp/mysql4.sock --pid-file=/seqweb/mysqldata/mysql4.pid
> --user=mysql --datadir=/seqweb/mysqldata
>
> 7023 pts/4 S 0:13 /seqweb/mysql-4.1.7/libexec/mysqld
> --defaults-file=/seqweb/mysqldata/my.cnf --basedir=/seqweb/mysql-4.1.7
> --datadir=/seqweb/mysqldata --pid-file=/seqweb/mysqldata/mysql4.pid
> --port=3306 --socket=/tmp/mysql4
>
> The problem is that I always have to give the --socket to all the clients,
> the port number is not enough. Ex:
>
>
put a .my.cnf file in the client's home directory that specifies the socket.
--
Gerald L. Clark
Supplier Systems Corporation
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
