From: Jeff Smelser <tradergt@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla Bug #109301 dev-db/mysql-4.1.14 stable request.
Date: Wed, 19 Oct 2005 12:10:10 -0500 [thread overview]
Message-ID: <200510191210.13078.tradergt@gmail.com> (raw)
In-Reply-To: <20051019124600.GB16978@peter.avira.local>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Wednesday 19 October 2005 07:46 am, Petre Rodan wrote:
> is that
> grant all privileges on 'DB'.* to 'user'@'localhost' identified by
> 'password'; deprecated in 4.1?
> because it inserts the line in mysql.users, but authentication is
> impossible :/
Do it here all the time..
> I had to use this syntax to get things going:
>
> GRANT USAGE ON *.* TO 'user'@'localhost' IDENTIFIED BY 'password' WITH
> MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0;
>
> GRANT ALL PRIVILEGES ON `DB`.* TO 'user'@'localhost';
>
> maybe it would be a Good Thing(TM) to add this to the upgrade document?
I have seen this when the mysql tables are out of scope with mysqld. Restart
is usually the only thing that fixes this..
Unless you have MAX_CONNECTIONS_PER_HOUR defined to low somewhere.. show
global viariables like 'MAX_CONNECTIONS_PER_HOUR' will show that.. (something
to the affect)
And you do NOT need the flush priv command after grant statements, only when
you go after the priv tables directly.
Jeff
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-19 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 14:06 [gentoo-dev] Bugzilla Bug #109301 dev-db/mysql-4.1.14 stable request Francesco R.
2005-10-17 14:47 ` Luca Longinotti
2005-10-17 15:11 ` nIr
2005-10-18 14:11 ` Francesco R.
2005-10-19 12:46 ` Petre Rodan
2005-10-19 13:30 ` Jeffrey Forman
2005-10-19 14:18 ` Petre Rodan
2005-10-19 17:04 ` John Myers
2005-10-19 17:10 ` Jeff Smelser [this message]
2005-10-20 8:35 ` [gentoo-dev] Unmasking dev-db/mysql-5 Francesco R.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510191210.13078.tradergt@gmail.com \
--to=tradergt@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox