From owner-freebsd-questions@FreeBSD.ORG Thu May 19 17:28:18 2005 Return-Path: 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 A781B16A4CE for ; Thu, 19 May 2005 17:28:18 +0000 (GMT) Received: from srvdmz13.oekb.co.at (srvdmz13.oekb.co.at [143.245.5.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id E28FF43D91 for ; Thu, 19 May 2005 17:28:14 +0000 (GMT) (envelope-from Ewald.Jenisch@oekb.at) X-SEF-Processed: 5_0_0_713__2005_05_19_19_28_12 X-SEF-EB89CDFD-460A-478E-BCAC-B017B9EC121B: 1 Received: from Unknown [143.245.2.191] by srvdmz13.oekb.co.at - SurfControl E-mail Filter (5.0); Do, 19 Mai 2005 19:28:12 +0200 Received: from aurora.oekb.co.at ([143.245.9.16]) by MAIL01.oekb.co.at with Microsoft SMTPSVC(5.0.2195.6713); Thu, 19 May 2005 19:28:11 +0200 Received: from aurora.oekb.co.at (localhost.oekb.co.at [127.0.0.1]) by aurora.oekb.co.at (8.13.3/8.13.1) with ESMTP id j4JHSBEd001151; Thu, 19 May 2005 19:28:11 +0200 (CEST) (envelope-from ej@aurora.oekb.co.at) Received: (from ej@localhost) by aurora.oekb.co.at (8.13.3/8.13.1/Submit) id j4JHSBxa001150; Thu, 19 May 2005 19:28:11 +0200 (CEST) (envelope-from ej) Date: Thu, 19 May 2005 19:28:11 +0200 From: Ewald Jenisch To: Lowell Gilbert Message-ID: <20050519172811.GA1113@aurora.oekb.co.at> References: <20050512085147.GA2114@aurora.oekb.co.at> <444qd7z2pi.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444qd7z2pi.fsf@be-well.ilk.org> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 19 May 2005 17:28:11.0738 (UTC) FILETIME=[2189A3A0:01C55C98] cc: freebsd-questions@freebsd.org Subject: Re: Tracking down "kern.ipc.maxpipekva exceeded" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2005 17:28:18 -0000 > > I would suggest keeping an eye on kern.ipc.pipekva and trying to > correlate any changes to the activity on the system at the time. I've already set this up - and it slowly (over days) is creeping up, e.g. May 12 18:00:58 CEST 2005: kern.ipc.pipekva: 114688 May 19 19:23:29 CEST 2005: kern.ipc.pipekva: 262144 At least I know what kern.ipc.pipekva is rising but, for me the most interesting part is, what actually is using up these resources? Is there any chance to get hold of the respective process/program? Regards, -ewald