From owner-freebsd-stable@FreeBSD.ORG  Wed Jun  9 21:12:46 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3D65116A4D0
	for <freebsd-stable@freebsd.org>;
	Wed,  9 Jun 2004 21:12:46 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1272643D4C
	for <freebsd-stable@freebsd.org>;
	Wed,  9 Jun 2004 21:12:46 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 0FE1E72DF2; Wed,  9 Jun 2004 14:12:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 0E49A72DB5; Wed,  9 Jun 2004 14:12:27 -0700 (PDT)
Date: Wed, 9 Jun 2004 14:12:27 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Kyle Mott <kyle@xraided.net>
In-Reply-To: <000301c44deb$4a78f1b0$1414a8c0@kyle>
Message-ID: <20040609141031.M41595@carver.gumbysoft.com>
References: <000301c44deb$4a78f1b0$1414a8c0@kyle>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-stable@freebsd.org
Subject: Re: Mysql Problems
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2004 21:12:46 -0000

On Tue, 8 Jun 2004, Kyle Mott wrote:

>
> I've now done buildworld twice, to no avail; for some reason, every 1-3
> minutes a new mysql process is started, for which looks like no apparent
> reason. Mysql on this machine is used very rarely, though it does get
> checked by Nagios regularly.

MySQL forks a child (or starts a new linuxthread depending on how its
configured) for each connection. The Nagios check would cause the new
process to be spawned. They should just exit, though. Check 'mysqladmin
processlist' or 'show processlist;' from the monitor to see who's
connected and what they're doing.

Its also possible that mysql will keep threads around once they've been
used to avoid exiting & respawning threads constantly. I haven't run MySQL
4.x and looked at it that closely.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org