From owner-freebsd-current@FreeBSD.ORG Mon Jan 19 21:01:05 2004 Return-Path: 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 2DB1916A4CE for ; Mon, 19 Jan 2004 21:01:05 -0800 (PST) Received: from mail.elcat.kg (imap.elcat.kg [212.42.96.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCAB143D1F for ; Mon, 19 Jan 2004 21:00:59 -0800 (PST) (envelope-from warlock@voip.kg) Received: by mail.elcat.kg (Postfix, from userid 6000) id 48F5B3CC9E8; Tue, 20 Jan 2004 10:00:51 +0500 (KGT) Received: from warcomp (warcomp.elcat.kg [212.42.96.26]) by mail.elcat.kg (Postfix) with ESMTP id 0FC593CC610; Tue, 20 Jan 2004 10:00:51 +0500 (KGT) From: Roman Streltsov Organization: Elcat To: Peter Losher , current@freebsd.org Date: Tue, 20 Jan 2004 10:00:49 +0500 User-Agent: KMail/1.5.4 References: <200401191506.07789.Peter_Losher@isc.org> In-Reply-To: <200401191506.07789.Peter_Losher@isc.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401201000.50224.warlock@voip.kg> Subject: Re: 'kern.maxpipekva exceeded' messages... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 05:01:05 -0000 On Tuesday 20 January 2004 04:06, Peter Losher wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In updating one of our authoritiative name servers to 5.2-REL, we > enountered after two days of running, kernel message like: > > kern.maxpipekva exceeded, please see tuning(7). > > appearing to the point to where you couldn't ssh into the box (because sshd > died w/ too many files opened). I see so mention of kern.maxpipekva on the > tuning man page, and greping only finds kern.ipc entries. > > % sysctl -a | grep pipekva > kern.ipc.maxpipekva: 10485760 > kern.ipc.maxpipekvawired: 5242880 > kern.ipc.pipekva: 131072 > kern.ipc.pipekvawired: 0 > > Are they the same, and if so, what's are the guidelines for increasing the > number? Yes, you can sure if look in sys/kern/sys_pipe.c In my case I just increased kern.ipc.maxpipekva in 16 times Also I do not why there is any mention in tuning(7) about maxpipe (in 5.2 current too) Good luck Roman