So with skip-name-resolve in my.cnf (and MySQL restarted), it should
be okay to have [EMAIL PROTECTED] in the GRANT table since localhost
resolves without DNS lookup? Or do I need to specify [EMAIL PROTECTED]
Sorry, just need to clarify this bit before changing a few things.
Thanks again.
Presently, I'm only using localhost for MySQL database user
privileges, e.g., :
[EMAIL PROTECTED] -- for all privileges on all databases
Do I need to change the above if I add skip-name-resolve to my.cnf?
(Since localhost is, I thought, not really part of DNS but just an
alias for
from http://dev.mysql.com/doc/refman/5.1/en/connecting.html
On Unix, MySQL programs treat the hostname |localhost| specially, in a
way that is likely different from what you expect compared to other
network-based programs. For connections to |localhost|, MySQL programs
attempt to connect to
is of a
confidential nature and Sender does not endorse distribution to
any party other than intended recipient. Sender does not
necessarily endorse content contained within this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date
distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
CC: [EMAIL PROTECTED]; mysql@lists.mysql.com
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Ancient, unsolved high-CPU problem -- vmstat, top
other than intended recipient. Sender does not
necessarily endorse content contained within this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25 +0200
For the longest time, I've had a strange
intended recipient.
Sender does not necessarily endorse content contained within this
transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25 +0200
For the longest time, I've had a strange problem
and Sender does not endorse distribution to any party other
than intended recipient. Sender does not necessarily endorse content
contained within this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25
nature and Sender does not endorse distribution to any party other
than intended recipient. Sender does not necessarily endorse
content contained within this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep
to
any party other than intended recipient. Sender does not
necessarily endorse content contained within this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25 +0200
For the longest time, I've had
: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25 +0200
For the longest time, I've had a strange problem with MySQL.
Basically, after a certain amount of time--sometimes a few days,
sometimes a couple weeks--its CPU usage will go from a steady
20-30%
to 80-90%. Actual load
, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25 +0200
For the longest time, I've had a strange problem with MySQL.
Basically, after a certain amount of time--sometimes a few days,
sometimes a couple weeks--its CPU usage will go from a steady
20-30%
to 80-90%. Actual load and number
this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU problem
Date: Mon, 22 Sep 2008 19:41:25 +0200
For the longest time, I've had a strange problem with MySQL.
Basically, after a certain amount of time--sometimes a few days,
sometimes
For the longest time, I've had a strange problem with MySQL.
Basically, after a certain amount of time--sometimes a few days,
sometimes a couple weeks--its CPU usage will go from a steady 20-30%
to 80-90%. Actual load and number of queries is the same, nothing else
changes.
If I shutdown
. This transmission is of a confidential
nature and Sender does not endorse distribution to any party other
than intended recipient. Sender does not necessarily endorse content
contained within this transmission.
From: [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Subject: Ancient, unsolved high-CPU
15 matches
Mail list logo
