12 messages in com.mysql.lists.perlRe: Accessing MySQL on another machin...
FromSent OnAttachments
Hal Vaughan25 Mar 2003 21:35 
Todd Finney25 Mar 2003 21:42 
Hal Vaughan25 Mar 2003 23:54 
Jochen Wiedmann26 Mar 2003 00:42 
Hal Vaughan26 Mar 2003 01:45 
Christopher Hicks26 Mar 2003 08:30 
Hal Vaughan26 Mar 2003 09:15 
Ulrich Borchers26 Mar 2003 10:03 
Hal Vaughan26 Mar 2003 12:07 
Ulrich Borchers26 Mar 2003 13:37 
Hal Vaughan26 Mar 2003 13:55 
Hal Vaughan26 Mar 2003 23:22 
Subject:Re: Accessing MySQL on another machine w/ DBI.pm
From:Hal Vaughan (ha@thresholddigital.com)
Date:03/26/2003 12:07:38 PM
List:com.mysql.lists.perl

On Wednesday 26 March 2003 01:03 pm, Ulrich Borchers wrote:

Maybe you have to make mysqld accept tcp connections. Those are disabled since 3.23.x versions (?) to make the default installation more secure. If my.cnf (possibly /etc/my.cnf) contains the line

skip-networking

then comment this line and restart mysqld.

#skip-networking

When I installed the latest (4.0.x -- whatever was just announced as stable), I had NO /etc/my.cnf. Now it reads:

[mysqld] socket=/var/lib/mysql/mysql.sock

[client] socket=/var/lib/mysql/mysql.sock

Could my setting the sockets to this particular file be effecting this?

If that does not work it might be of importance in which order mysql parses the db/user tables to determine access privileges. Maybe you have conflicting entries there. You could remove all but the "hal" user and allow access from % with alle privs for testing purpose.

I'll try that. Since this is all in a lan anyway, I may just allow access from all on that system (in a few months it will all be ported over to other systems anyway) with a password.

Thanks!

Hal

On 26 Mar 2003 at 12:15, Hal Vaughan wrote:

DBI->connect(database=lopas;host=mysqlhost;port=3306) failed: Access denied for user: 'hal@192.168.1.11' to database 'MaliningList' at ./test.pl line 13

Now I actually get an error that includes the name of the database. I don't know if that's better or worse....