From owner-freebsd-questions@FreeBSD.ORG Thu May 19 17:44:28 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 869AD16A4D0 for ; Thu, 19 May 2005 17:44:28 +0000 (GMT) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D836643D8D for ; Thu, 19 May 2005 17:44:27 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 12451 invoked from network); 19 May 2005 17:44:21 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 May 2005 17:44:21 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 994492E; Thu, 19 May 2005 13:44:20 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Ewald Jenisch References: <20050512085147.GA2114@aurora.oekb.co.at> <444qd7z2pi.fsf@be-well.ilk.org> <20050519172811.GA1113@aurora.oekb.co.at> From: Lowell Gilbert Date: 19 May 2005 13:44:20 -0400 In-Reply-To: <20050519172811.GA1113@aurora.oekb.co.at> Message-ID: <447jhvm7pn.fsf@be-well.ilk.org> Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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:44:28 -0000 Ewald Jenisch writes: > > > > 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? ipcs(1) might help.