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 th
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
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.
_
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the
official business of Sender. This transmission is of a
confidential nature and Sender does not endorse distribution to
any party other than intended recipient. Sender does not
necessarily e
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 probl
ot
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 with MyS
pient. 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 p
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 with MySQL.
> Basically, after a certain amount of ti
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,
> s
ntial 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
> D
of Sender. 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: Ancie
al
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
> Da
the official
>> business of Sender. 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.
>>
>&
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%
>
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
0x0 in ?? ()
If you see that, get rid of DNS lookups.
- Original Message -
From: "Arnaud Pignard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 16, 2004 7:06 PM
Subject: Re: Repeated 100% CPU problem in FreeBSD
> Hi !
>
> Anyone find a s
- Original Message -
From: "Arnaud Pignard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 16, 2004 7:06 PM
Subject: Re: Repeated 100% CPU problem in FreeBSD
> Hi !
>
> Anyone find a solution for this problem ?
>
> We have 2 m
Hi !
Anyone find a solution for this problem ?
We have 2 mysql server with same problem. Happen like every 1-2 months.
Regards,
--
Arnaud Pignard ([EMAIL PROTECTED])
Frontier Online - Opérateur Internet
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscri
SQL
I have the same situation.
I set skip-name-resolve in my.cnf.
But sometimes mysqld get all CPU.
I can't notice strong dependences between name resoving and mysqld stuped.
> Hello,
>
> Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9
> system. However, today, unexplicably
On Thu, Nov 27, 2003 at 06:25:38PM -0600, Dan Nelson wrote:
> In the last episode (Nov 27), Chris Elsworth said:
> > Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9
> > system. However, today, unexplicably, it's run into the same problem
> > 3 times now; a couple of the thread
In the last episode (Nov 27), Chris Elsworth said:
> Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9
> system. However, today, unexplicably, it's run into the same problem
> 3 times now; a couple of the threads suddenly start eating 100% CPU
> for no good reason while doing a
Hello,
Most of the time, MySQL 4.0.16 runs absolutely fine on my FreeBSD 4.9
system. However, today, unexplicably, it's run into the same problem 3
times now; a couple of the threads suddenly start eating 100% CPU for
no good reason while doing a SELECT. They'll sit there until I kill
them, which
Hello,
On our server we currently have, what I think, is a problem. We run mysql
for some time now, but every time a query is loaded the mysqld uses more
then 50 % of the CPU. In some cases it even uses 99,9 % of the cpu for a
second or 2.
I find this very strange myself. The table that's used
23 matches
Mail list logo
