From owner-freebsd-performance@FreeBSD.ORG  Fri Apr  4 17:12:01 2008
Return-Path: <owner-freebsd-performance@FreeBSD.ORG>
Delivered-To: freebsd-performance@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 28B4D106564A
	for <freebsd-performance@freebsd.org>;
	Fri,  4 Apr 2008 17:12:01 +0000 (UTC)
	(envelope-from Jinmei_Tatuya@isc.org)
Received: from mon.jinmei.org (mon.jinmei.org [IPv6:2001:4f8:3:36::162])
	by mx1.freebsd.org (Postfix) with ESMTP id 0FAD58FC27
	for <freebsd-performance@freebsd.org>;
	Fri,  4 Apr 2008 17:12:01 +0000 (UTC)
	(envelope-from Jinmei_Tatuya@isc.org)
Received: from dhcp-191.sql1.isc.org (unknown
	[IPv6:2001:4f8:3:bb:1584:aac1:f118:4b12])
	by mon.jinmei.org (Postfix) with ESMTP id C1A2433C2E;
	Fri,  4 Apr 2008 10:12:00 -0700 (PDT)
Date: Fri, 04 Apr 2008 10:12:00 -0700
Message-ID: <m2bq4pk0in.wl%Jinmei_Tatuya@isc.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<Jinmei_Tatuya@isc.org>
To: Attila Nagy <bra@fsn.hu>
In-Reply-To: <47F63C82.7060502@fsn.hu>
References: <475B0F3E.5070100@fsn.hu> <m2lk6g71bc.wl%Jinmei_Tatuya@isc.org>
	<479DFE74.8030004@fsn.hu> <m2k5ltke09.wl%Jinmei_Tatuya@isc.org>
	<479F02A7.9020607@fsn.hu> <m24pcwt5b7.wl%Jinmei_Tatuya@isc.org>
	<47A614E9.4030501@fsn.hu> <m2wspkpl7r.wl%Jinmei_Tatuya@isc.org>
	<47A77A13.6010802@fsn.hu> <m2zlueohxk.wl%Jinmei_Tatuya@isc.org>
	<47B1D2F4.5070304@fsn.hu> <m2tzkexdo7.wl%Jinmei_Tatuya@isc.org>
	<47B2DD62.6020507@fsn.hu> <m2abm4y4by.wl%Jinmei_Tatuya@isc.org>
	<47BAE0B3.4090004@fsn.hu> <m2pruse24g.wl%Jinmei_Tatuya@isc.org>
	<47F4F63E.80703@fsn.hu> <m21w5mltki.wl%Jinmei_Tatuya@isc.org>
	<47F63C82.7060502@fsn.hu>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Fri, 04 Apr 2008 17:55:58 +0000
Cc: freebsd-performance@freebsd.org, bind-users@isc.org
Subject: Re: max-cache-size doesn't work with 9.5.0b1
X-BeenThere: freebsd-performance@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Performance/tuning <freebsd-performance.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-performance>
List-Post: <mailto:freebsd-performance@freebsd.org>
List-Help: <mailto:freebsd-performance-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2008 17:12:01 -0000

At Fri, 04 Apr 2008 16:34:42 +0200,
Attila Nagy <bra@fsn.hu> wrote:

> No effect, the process grows happily. I don't have a core dump.

Hmm, sorry, then I have no further idea of chasing the problem.  A few
points that may help:
- can you show the diff you applied to bin/named/main.c when you added
  the malloc_options?
- regarding the core dump, you may have to set the
  "kern.sugid_coredump" sysctl variable to 1, and make sure that then
  directly where named resides (which should be under /etc/bind/ with
  your config) is writable for the uid of the process.  Or, simply run
  named as a root without specifying -u for the debugging purpose.
- is it possible for me to get access to the test machine, or to get
  the query pattern so that I can reproduce the problem by myself?  As
  I stated before, I tried to reproduce it with my box that has the
  similar system environment, but I failed to see the problem.

Thanks,

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.