mysql-connect is working very slow

[Marten Lehmann]

Hello,
this weekend, one of our caching nameservers failed. Since then, all 
mysql-connects were running very slow. I removed the failing nameserver 
in /etc/resolv.conf. Later, I was setting up another caching nameserver 
instead and inserted it in /etc/resolv.conf. I rebooted the 
mysql-machine. Nothing helped so far. What does mysql take so long to 
connect? I guess it's some sort of lookup, but I don't know what in 
detail. Since there's no failing nameserver anymore, I don't understand, 
why it is still taking so long. Is it performing ident lookups also? How 
can I check which nameserver mysql is using? I also tried 
--skip-name-resolve in the mysqld-startup, but this also didn't help. 
But connecting from localhost is fast as always.

Regards
Marten
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

mysql-connect is working very slow (2)

[Marten Lehmann]

Hello,
regarding --skip-name-resolve: I read, that values in the Host-column of 
the mysql-authorization must be localhost or ip-addresses to work. Since 
everyone can connect from everywhere, I used 'localhost' and '%'. Is % 
treated the same? Is the ip-address-rule obligatory or just a 
should-have? Is --skip-name-resolve treated as if wouldn't be there if 
the values in Host aren't of type ip-address?

Regards
Marten

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]