From owner-freebsd-questions@FreeBSD.ORG Thu May 19 17:54:05 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 58BD116A4CE for ; Thu, 19 May 2005 17:54:05 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7DA243DB7 for ; Thu, 19 May 2005 17:54:04 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j4JHs1vr089783; Thu, 19 May 2005 12:54:01 -0500 (CDT) (envelope-from dan) Date: Thu, 19 May 2005 12:54:01 -0500 From: Dan Nelson To: Ewald Jenisch Message-ID: <20050519175401.GE82926@dan.emsphone.com> References: <20050512085147.GA2114@aurora.oekb.co.at> <444qd7z2pi.fsf@be-well.ilk.org> <20050519172811.GA1113@aurora.oekb.co.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050519172811.GA1113@aurora.oekb.co.at> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i cc: Lowell Gilbert 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:54:05 -0000 In the last episode (May 19), Ewald Jenisch said: > > 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? Pipes :) > Is there any chance to get hold of the respective process/program? lsof | grep PIPE should do the trick. Lsof's SIZE/OFF column shows the allocated buffer size for that pipe. Most of the time you'll see either 0 (pipe has never been used) or 16384 (default value). -- Dan Nelson dnelson@allantgroup.com