Thanks for the tips, all. Looks like we've got it restored via --skip-grant-tables and restoring some missing user rows (which caused me not to be able to see DBs in 'show databases'). I was also confused about being able to load an empty string '' into the non-null mysql.user.password field. Thanks again.
On Tuesday 25 August 2009 @ 21:51, Walter Heck - OlinData.com wrote: > Is there a specific reason you cannot do it with > --skip-grant-table? > > You should theoretically also be able to overwrite the files > user.* (there should be 3) in /var/lib/mysql/mysql/ (replace > everything up to and including teh first mysql in that path > with your mysql data dir) when the server is stopped with a > copy from a fresh install. That will wipe all users in your > database though, and might have unforeseen consequences > depending on what you had defined before. > > Backup first though! > > Walter > > On Wed, Aug 26, 2009 at 03:33, Joe<mysql....@bluepolka.net> wrote: > > I'm trying to get back to an earlier state where we started > > mysqld withOUT --skip-grant-tables but the root user had no > > password. Yes, insecure, but we're in restoration mode > > here. > > > > How do I reset/revert the root password to no password > > without running with --skip-grant-tables? > > > > Thanks in advance. > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: > > http://lists.mysql.com/mysql?unsub=li...@olindata.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org