Thanks for that.
I had found that in the manual, but as I used /etc/init.d/mysql.server to
stop and start mysqld I thought that I needed to pass the
--skip-grant-tables to that.
I've now found out differently!
I seem to have got it cracked now.
Many thanks,
Derek...
-----Original Message-----
From: Richard Dice [mailto:[EMAIL PROTECTED]]
Sent: 22 September 2001 16:20
To: Derek Fage
Cc: 'R Talbot'; [EMAIL PROTECTED]
Subject: Re: Help - I'm completely locked out of mysql
The official answer to your problem can be found in the mysql manual.
This could very well be installed on your computer, somewhere (different
packaging systems put it in different places, and you may or may not have
included the mysql documentation package on your system). Regardless,
you can _always_ go to the "Documentation" section on the mysql web site.
This is probably a better first place to go than "searching the archives",
which I assume means the mailing list archives. Still, I'm surprised you
didn't find anything appropriate in the archives, since this question
is asked so often.
http://www.mysql.com/documentation/mysql/bychapter/manual_Problems.html#Rese
tting_permissions
It's mysqld that requires the --skip-grant-tables option, not mysql
requiring a -Skip-grant option. (That's wrong in 2 different ways.)
Note that the information provided at this link is _not_ just a
plug-and-play
solution. It will talk about things that you may not have previous
experience with. For instance, "mysqld". This is the mysql server
(daemon).
Possibly, your computer automatically runs mysqld whenever you start it up,
due to an entry in /etc/init.d/mysqld, or /etc/rc.d/init.d/mysql, or any
number of other similar possibilities. (If you're using SlackWare Linux
or another BSD-inspired system, there won't be an "init.d" directory, if I
recall correctly after all these years...)
Even then, the /etc/init.d/mysqld script probably doesn't have within it
a reference to "mysqld" directly. It might invoke the "safe-mysqld"
script, or something entirely different. You could dig a while before
you finally discover the thing that does the call to "mysqld". I
recommend you find it just so that you understand how mysqld is called,
before calling it yourself directly.
Other suggestions....
* rather than using the "kill" command they mention here, you might just
want to do "/etc/init.d/mysqld stop" (or whatever is similar, given
the specifics of your system)
* maybe you haven't run into the "GRANT" command yet -- read up on it;
it's in the manual, too
* don't forget FLUSH PRIVILEGES! If you don't know what this means,
read up about it in the manual.
Good luck...
Cheers,
Richard
--
----------------------------------------------------------------------------
Richard Dice * Personal 416 841 7365 * Fax 416 841 7364
ShadNet Creator * http://shadnet.shad.ca/ * [EMAIL PROTECTED]
Occasional Writer, HotWired * http://www.hotwired.com/webmonkey/
"squeeze the world 'til it's small enough to join us heel to toe"
- jesus jones
***************************************************************************************
Any views expressed in this message are those of the individual sender,
except where the sender states them to be the views of Foreshore Limited.
This e-mail is intended only for the individual or entity to which it is
addressed and contains information that is private and confidential. If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to [EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
