On Saturday 31 July 2010 4:40:14 chaim rieger wrote: > Another thing I just noticed > > In your first example you are using localhost, which probably means you are > connecting via network > > The second option you don't define a host, which means you're prolly using > socket connection
Oh, whoops - my bad for not being consistent with the examples. /usr/local/mysql/bin/mysql -h localhost -u scripts Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 32 to server version: 4.1.14-standard Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> \q ... it also works if I supply the '-p' option, but just hit <enter> at the password prompt: /usr/local/mysql/bin/mysql -h localhost -u scripts -p Enter password: <enter> Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 33 to server version: 4.1.14-standard Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> I'm completely baffled as to why I can _only_ login _without_ a password... but only for that one user, 'scripts'. Everything else works as expected. Is there some other auth table, or a config file or something that could cause such behavior. (I also don't understand why this would suddenly start occurring - seems suspicious) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
