From owner-freebsd-current@FreeBSD.ORG  Fri Jan  9 22:11:16 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E8F4716A4CE
	for <current@freebsd.org>; Fri,  9 Jan 2004 22:11:16 -0800 (PST)
Received: from mail.elcat.kg (imap.elcat.kg [212.42.96.15])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2C98A43D53
	for <current@freebsd.org>; Fri,  9 Jan 2004 22:11:13 -0800 (PST)
	(envelope-from warlock@voip.kg)
Received: by mail.elcat.kg (Postfix, from userid 6000)
	id CBD703CE104; Sat, 10 Jan 2004 11:11:05 +0500 (KGT)
Received: from warcomp (warcomp.elcat.kg [212.42.96.26])
	by mail.elcat.kg (Postfix) with ESMTP id 67B6C3CE03A
	for <current@freebsd.org>; Sat, 10 Jan 2004 11:11:05 +0500 (KGT)
From: Roman Streltsov <warlock@voip.kg>
Organization: Elcat
Date: Sat, 10 Jan 2004 11:11:04 +0500
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Disposition: inline
To: current@freebsd.org
Content-Type: text/plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Message-Id: <200401101111.04908.warlock@voip.kg>
X-Mailman-Approved-At: Sat, 10 Jan 2004 06:02:43 -0800
Subject: 5.2-RC and kern.maxpipekva exceeded
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2004 06:11:17 -0000

Hello current,

I'd got message after simultaneous coredumping network program (I suspect pipe 
leak in code) and failing of watchdog shell script.

kern.maxpipekva exceeded, please see tuning(7).

I guess I should tune 
kern.ipc.maxpipekva and kern.ipc.maxpipekvawired

But I haven't any clue how to make the watcher is reliable. Statment like 
PIDS=`ps -ax | grep -v grep | grep mydaemon | awk '{print $1}'` looks like 
potential troublemaker.

For RC that is odd behavior and on 5.1 (and earler) box I hadn't never see 
synchronous fails for several programs.

By the way, there wasn't any mention about kern.maxpipekva in tuning(7)

Could somebody give me idea how resolve the trouble?
Thanx
Roman