Hi Olivier & all!
Problems were: PMA_INT_VERSION < 30010 instead of PMA_INT_VERSION >= 30010 :)
I'm afraid this isn't true ;) The socket setting is available since php 3.0.10 only then $server_socket should be empty if PMA_INT_VERSION < 30010.
and fact that $connect_func() is used twice in lib.inc.php3
Oups, you're right... I must be drunk we I merged the patch. But the name of this second link is $link and not $dbh.
OK, I've done some advanced tests with the socket patch and found also that phpMyAdmin runs even with a garbage socket path. It seems that php try to use a kind of default socket path if the one defined in the phpMyAdmin configuration file is not valid or scans all available sockets till it finds the convenient one (indeed it takes far much time to load phpMyAdmin whith an invalid socket path).
Loïc
______________________________________________________________________________ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP... http://www.ifrance.com/_reloc/email.emailif
On Tue, Aug 21, 2001 at 11:34:53AM +0200, Loïc wrote:
Hi Olivier & all!
Problems were: PMA_INT_VERSION < 30010 instead of PMA_INT_VERSION >= 30010 :)
I'm afraid this isn't true ;) The socket setting is available since php 3.0.10 only then $server_socket should be empty if PMA_INT_VERSION < 30010.
shit :) but, why on earth did it worked fine that way on my server ? :) Mmmm...
and fact that $connect_func() is used twice in lib.inc.php3
Oups, you're right... I must be drunk we I merged the patch. But the name of this second link is $link and not $dbh.
ok, and shouldn't wake up so early to work on pma :)
OK, I've done some advanced tests with the socket patch and found also that phpMyAdmin runs even with a garbage socket
mmm, and now with the current cvs I can't connect anything. Still must be something wrong somewhere...
Olivier