>It is skip-name-resolve - I just wrote it by memory and was wrong. There is
>also a nice piece on "Access denied" errors at
Thanks - I'd already read that.
I've also discovered that its generating log entries (I've got a
3 Gbyte log file) even though I havent asked for them.
How can I turn this off? Do I have to use -l /dev/null ?
I'm definitely starting to suspect some compiled-in options.
Do you know how I can discover what the compile-time options
were? I cant (yet) find anything relevant in the MySQL Ref manual
Apologies for the continual questions - I'm new to 4.1 as of 1 week ago.
>On Friday 02 September 2005 16:35, T. Horsnell wrote:
>> >Does the 10.4.0.101 reverse resolve to a specific hostname? If it does you
>> > are probably running MySQL with the skip_hostname_resolve option and if
>> > it doesn't there is no way the MySQL server could tell from which host
>> > the request is comming.
>> It does. The problem exists for all remote hosts which try to connect,
>> and they all resolve. So far as I'm aware, I'm not using the
>> skip_hostname_resolve (do you mean skip-name-resolve ?) option:
>> # ps -ef | grep mysql
>> mysql 71401 1 0.0 Aug 31 ?? 0:00.01
>> /usr/local/mysql/bin/safe_mysqld mysql 71876 71401 0.0 Aug 31 ??
>> 04:22:56 /usr/local/mysql/bin/mysqld
>> --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data
>> and I have no /usr/local/mysql/data/my.cnf
>> # ls -l /usr/local/mysql/data/*.cnf
>> ls: No match.
>> Could it be that the server-binary was compiled with skip-name-resolve ?
>> >My opinion is that it is always better to use the IP-addresses instead of
>> > the hostnames and use skip_hostname_resolve - the connection overhead
>> > will be smaller this way.
>> >You can also check the comments on
>> Thanks, I'll do this.
>> >Dobromir Velev
>> >On Friday 02 September 2005 13:38, T. Horsnell wrote:
>> >> After replacing a 3.23.28 server with 4.1.14 server binaries on an
>> >> running Tru64 5.1B, I get things like:
>> >> ERROR 1045 (28000): Access denied for user 'tsh'@'10.4.0.101' (using
>> >> password: YES)
>> >> when trying to connect from a remote host.
>> >> The problem goes away if I replace hostnames by IP addresses
>> >> in the mysql 'user' tables. I see from the archives that this
>> >> problem has been reported recently by others. Is there a fix?
>> >> (apart from changing every relevant entry in the user tables)
>> >> I cant see anything relevant in the Buglists.
>> >> Cheers,
>> >> Terry.
>> >MySQL General Mailing List
>> >For list archives: http://lists.mysql.com/mysql
>> >To unsubscribe:
>> > http://lists.mysql.com/mysql?unsub=1