Peter Burden <[EMAIL PROTECTED]> wrote: > I'm sure there's an answer somewhere but the 900+ page > manual is a bit overwhelming. I have MySQL 4.1 running on one > machine and I'd like to access using the client software I > alerady have on another machine which was built against 3.23.33. > Access is via command line client (mysql), PHP and C-API - all > obviously built against the same client library. > I gather from the manual (brief note at top of page 222) > that 4.1 has a different way of handling passwords which is > why a mysql connection failed with error 1249 about authentication > protocols. Is there any way round this? I really don't want to > have two separate sets of client stuff around and I'm not ready > to switch a production system to 4.1
You can run mysqld with --old-passwords option or put old-passwords to the my.cnf: [mysqld] old-passwords -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
