From owner-freebsd-bugs@FreeBSD.ORG Thu Mar 9 11:17:15 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EC0E16A422; Thu, 9 Mar 2006 11:17:15 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D268B43D46; Thu, 9 Mar 2006 11:17:14 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k29BHET7014674; Thu, 9 Mar 2006 11:17:14 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k29BHEi6014670; Thu, 9 Mar 2006 11:17:14 GMT (envelope-from linimon) Date: Thu, 9 Mar 2006 11:17:14 GMT From: Mark Linimon Message-Id: <200603091117.k29BHEi6014670@freefall.freebsd.org> To: techmed@bellatlantic.net, linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: misc/94265: FreeBSD 6.0 + MySQL = NO X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2006 11:17:15 -0000 Synopsis: FreeBSD 6.0 + MySQL = NO State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Thu Mar 9 11:10:00 UTC 2006 State-Changed-Why: > FreeBSD 6.0 is absolutely UNUSABLE with MySQL under any production > environment [...] There are known performance problems with FreeBSD and MySQL which are being worked on (see the MySQL entry on wikitest.FreeBSD.org). The default tuning does not work well for MySQL. There may be other, underlying, problems having to do with MySQL assumptions that it is running Linux. > I don't really have time to submit bug reports, or get into detail, I'm > too busy. As one of the chief people who works on the incoming Problem Reports, I have to say that I'm disappointed in this attitude. The majority of people who work on FreeBSD are volunteers and it is only by volunteer effort and community participation that FreeBSD advances. In any case this problem report is so non-specific that it's really not possible to take any direct action on it as an individual item. I would rather keep the PR database just for the things that we can readily identify and fix. http://www.freebsd.org/cgi/query-pr.cgi?pr=94265