From owner-freebsd-current@FreeBSD.ORG  Tue Nov 18 13:29:43 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DB3F616A4CE
	for <current@freebsd.org>; Tue, 18 Nov 2003 13:29:43 -0800 (PST)
Received: from web14102.mail.yahoo.com (web14102.mail.yahoo.com
	[216.136.172.132])
	by mx1.FreeBSD.org (Postfix) with SMTP id 6D71443FDD
	for <current@freebsd.org>; Tue, 18 Nov 2003 13:29:42 -0800 (PST)
	(envelope-from cguttesen@yahoo.dk)
Message-ID: <20031118212942.15142.qmail@web14102.mail.yahoo.com>
Received: from [194.248.174.33] by web14102.mail.yahoo.com via HTTP;
	Tue, 18 Nov 2003 22:29:42 CET
Date: Tue, 18 Nov 2003 22:29:42 +0100 (CET)
From: =?iso-8859-1?q?Claus=20Guttesen?= <cguttesen@yahoo.dk>
To: Scott Long <scottl@freebsd.org>
In-Reply-To: <20031118135038.T34253@pooker.samsco.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
cc: current@freebsd.org
Subject: Re: FreeBSD current, apache and php4 woes
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2003 21:29:44 -0000

Hi.

>>> Add one of the two lines to /boot/loader.conf:
>>>
>>> kern.vn.kmem.size=350000000
>>> or
>>> kern.maxvnodes=150000
>>>
>>> The first one is probably the better choice for
you
>>> since
>>> the very nature of what you are doing demands
>>> that you touch a lot of vnodes.

>> 1. added kern.vm.kmem.size=450000000
>> 2. clean up tmp-files older than 4 hours every hour

> I forgot to mention in the last email that
> kern.maxvnodes
> will still scale upwards as you increase
> kern.vm.kmem.size.
> So you might want to set a hard limit on it so you
> don't
> continue to run into problems.  A value of 200,000
> is probably good in your case.
> 

A sysctl kern.maxvnodes gives me 134675, but it's been
added as a safetyprecaution to /boot/loader.conf.

regards
Claus


Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan