On Sat, 17 Aug 2002, Jeremy Zawodny wrote:
On Fri, Aug 09, 2002 at 04:20:42PM -0400, David Miller wrote:
On Sun, 4 Aug 2002, Jeremy Zawodny wrote:
Hi Jeremy;
I didn't think my server would be doing any name resolution, particularly
while replace()ing millions of rows in a table.
On Fri, Aug 09, 2002 at 04:20:42PM -0400, David Miller wrote:
On Sun, 4 Aug 2002, Jeremy Zawodny wrote:
Hi Jeremy;
I didn't think my server would be doing any name resolution, particularly
while replace()ing millions of rows in a table. That said,
--skip-name-resolve *seems* to have
On Sun, 4 Aug 2002, Jeremy Zawodny wrote:
Hi Jeremy;
I didn't think my server would be doing any name resolution, particularly
while replace()ing millions of rows in a table. That said,
--skip-name-resolve *seems* to have helped. It's definately still
failing, and the ktrace is the same, so
In the last episode (Aug 09), David Miller said:
On Sun, 4 Aug 2002, Jeremy Zawodny wrote:
On Sat, Aug 03, 2002 at 11:59:56PM -0400, [EMAIL PROTECTED] wrote:
I didn't think my server would be doing any name resolution,
particularly while replace()ing millions of rows in a table. That
On Fri, Aug 09, 2002 at 04:04:10PM -0500, Dan Nelson wrote:
A coredump of this state + gdb thread apply all bt might be interesting.
Hmm. Looks like a problem we solve recently, but yours is a bit
different. We found that FreeBSD's not-so-thread-safe
gethostbyname_r() causes
I thought I got this through the list, but it doesn't show up in the
search, and I didn't get any responses...
-- Forwarded message --
Date: Wed, 31 Jul 2002 23:14:13 -0400 (EDT)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: SIGPROF problem in FreeBSD 4.6
This almost
On Sat, Aug 03, 2002 at 11:59:56PM -0400, [EMAIL PROTECTED] wrote:
Symptoms:
mysqld locks itself in a tight loop, consuming all available CPU cycles.
a simple kill sometimes kills the daemon, other times a -9 is required.
While in this state, any access to the daemon stops - mysql queries
This almost belongs on the bugs list, but I don't have a stable, sure way
to trigger it.
Symptoms:
mysqld locks itself in a tight loop, consuming all available CPU cycles.
a simple kill sometimes kills the daemon, other times a -9 is required.
While in this state, any access to the daemon stops
