Date: Thu, 19 May 2005 12:54:01 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Ewald Jenisch <a@jenisch.at> Cc: freebsd-questions@freebsd.org Subject: Re: Tracking down "kern.ipc.maxpipekva exceeded" Message-ID: <20050519175401.GE82926@dan.emsphone.com> In-Reply-To: <20050519172811.GA1113@aurora.oekb.co.at> References: <20050512085147.GA2114@aurora.oekb.co.at> <444qd7z2pi.fsf@be-well.ilk.org> <20050519172811.GA1113@aurora.oekb.co.at>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050519175401.GE82926>