Hi all,
We have many Mysql's running here, and just to tell you, there
are fixes/workarounds for the behaviour you see:
FreeBSD 4.8 / 4.9 / 4.10 :
--
Compile port with WITH_LINUXTHREADS=YES or remove tcpwrappers
support manually from the build if it hangs with libc_r.
On Mon, 2 Aug 2004, Martin Blapp wrote:
Hi all,
We have many Mysql's running here, and just to tell you, there
are fixes/workarounds for the behaviour you see:
FreeBSD 4.8 / 4.9 / 4.10 :
--
Compile port with WITH_LINUXTHREADS=YES or remove tcpwrappers
On Sat, 31 Jul 2004, adp wrote:
I recently posted the following message to MySQL discussion list. The
response there, and the one I keep finding on Google, is that this is a
long-standing issue betweeen FreeBSD and MySQL. For me this has been
happening since FreeBSD 4.4.
I had that problem a
On Sun, 2004-08-01 at 04:08, adp wrote:
FreeBSD 4.4, 4.7, 4.9, 4.10
MySQL 3.x and 4.x
Typical load: 50 qps
With and without replication enabled.
Some sites are SELECT heavy, some are INSERT heavy.
For one site I think we will be moving from FreeBSD to Linux for the MySQL
servers since
On Sat, Jul 31, 2004 at 10:08:32PM -0500, adp wrote:
Any help on this? Googling shows a long history of people having these
problems but no solutions. Please don't give me a URL to a Google showing
others having this problem--I've seen that and more. I want to know if there
is a solution. Any
On Saturday 31 July 2004 21:08, adp wrote:
I recently posted the following message to MySQL discussion list. The
response there, and the one I keep finding on Google, is that this is a
long-standing issue betweeen FreeBSD and MySQL. For me this has been
happening since FreeBSD 4.4.
I don't
On Sat, Jul 31, 2004 at 10:08:32PM -0500, adp wrote:
I recently posted the following message to MySQL discussion list. The
response there, and the one I keep finding on Google, is that this is a
long-standing issue betweeen FreeBSD and MySQL. For me this has been
happening since FreeBSD 4.4.
I recently posted the following message to MySQL discussion list. The
response there, and the one I keep finding on Google, is that this is a
long-standing issue betweeen FreeBSD and MySQL. For me this has been
happening since FreeBSD 4.4.
I have one site where we are going to have to move to
removed hackers@, database@
Before the rest of the message ... I think it'd be best not to shotgun
your mails like this...
adp wrote:
I recently posted the following message to MySQL discussion list. The
response there, and the one I keep finding on Google, is that this is a
long-standing issue
removed hackers@, database@
Before the rest of the message ... I think it'd be best not to shotgun
your mails like this...
Hello.
I would disagree with this. This is obviously both database@ and
questions@ appropriate. I also feel that it is hackers@ appropriate as it
deals with an old,
10 matches
Mail list logo