From owner-freebsd-questions@FreeBSD.ORG Wed Jul 19 18:37:17 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1594C16A4DD for ; Wed, 19 Jul 2006 18:37:17 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id D141943D86 for ; Wed, 19 Jul 2006 18:37:02 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 443525D44; Wed, 19 Jul 2006 14:37:02 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ohoRYEcuBVw; Wed, 19 Jul 2006 14:37:01 -0400 (EDT) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 788B05C30; Wed, 19 Jul 2006 14:37:01 -0400 (EDT) In-Reply-To: <653A9EA4-19F7-41E8-BDD4-E0906C997D6E@dm1.net> References: <407487AA-A1C4-4581-A7EA-2FBC68E284C6@dm1.net> <653A9EA4-19F7-41E8-BDD4-E0906C997D6E@dm1.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <96460F2A-A74E-4A5F-ACB5-A40ABD133298@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Wed, 19 Jul 2006 14:37:00 -0400 To: Thaddeus Quintin X-Mailer: Apple Mail (2.752.2) Cc: freebsd-questions@freebsd.org Subject: Re: Memory usage for MySQL X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 18:37:17 -0000 On Jul 19, 2006, at 2:31 PM, Thaddeus Quintin wrote: > I already took care of that, it was in my first email- >>> I tweaked /boot/loader.conf to allow larger data size for >>> processes already (rebooted after changes)- >>> kern.maxdsiz="1395864371" # 1.3GB >>> kern.dfldsiz="1395864371" # 1.3GB >>> kern.maxssiz="134217728" # 128MB > > From what I read, that should do it, but I still get those start up > errors before MySQL decides to run. Maybe it has something to do > with how quickly MySQL is asking for memory? Or maybe it's trying to ask for a big shared memory segment...? -- -Chuck