From owner-freebsd-current@FreeBSD.ORG Mon Nov 10 16:54:56 2003 Return-Path: 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 6711916A4CE for ; Mon, 10 Nov 2003 16:54:56 -0800 (PST) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A084F43FBF for ; Mon, 10 Nov 2003 16:54:54 -0800 (PST) (envelope-from wilkinsa@squirm.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id hAB0sn66008061 for ; Tue, 11 Nov 2003 11:24:49 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Tue, 11 Nov 2003 11:24:44 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id hAB0jRo31401; Tue, 11 Nov 2003 11:15:27 +1030 (CST) Received: from squirm.dsto.defence.gov.au ([131.185.40.211]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id WHC7DRR6; Tue, 11 Nov 2003 11:15:18 +1030 Received: from squirm.dsto.defence.gov.au (localhost [127.0.0.1]) by squirm.dsto.defence.gov.au (8.12.10/8.12.10) with ESMTP id hAB0jQ9H042930 ; Tue, 11 Nov 2003 11:15:27 +1030 (CST) (envelope-from wilkinsa@squirm.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squirm.dsto.defence.gov.au (8.12.10/8.12.10/Submit) id hAB0jOUZ042925; Tue, 11 Nov 2003 11:15:24 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 11 Nov 2003 11:15:24 +1030 From: Alex Wilkinson To: Bruce Evans Message-ID: <20031111004523.GE14579@squirm.dsto.defence.gov.au> References: <20031110164513.GA828@bewilderbeast.blackhelicopters.org> <20031111042518.I857@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20031111042518.I857@gamplex.bde.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: erroneous message from locked-up machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 00:54:56 -0000 Can someone please elaborate on the acronym KVA ? $ sysctl -d kern.ipc.maxpipekva kern.ipc.maxpipekva: Pipe KVA limit This doesn't tell me enough. - aW On Tue, Nov 11, 2003 at 04:46:47AM +1100, Bruce Evans wrote: > > I came in to work today to find one of my -current machines unable to > > open a pipe. (This probably had a lot to do with the spamd that went > > stark raving nutters overnight, but that's a separate problem.) A > > power cycle fixed the problem, but /var/log/messages was filled with: > > > > Nov 10 11:05:44 bewilderbeast kernel: kern.maxpipekva exceeded, please see tuning(7). > > > > Interesting. > > > > bewilderbeast~;sysctl kern.maxpipekva > > sysctl: unknown oid 'kern.maxpipekva' > > bewilderbeast~; > > The following patch fixes this and some nearby style bugs: > - source style bug: line too line > - output style bugs: comma splice, verboseness (helps make the source line > too long), and kernel message terminated with a ".". > > %%% > Index: sys_pipe.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v > retrieving revision 1.158 > diff -u -2 -r1.158 sys_pipe.c > --- sys_pipe.c 9 Nov 2003 09:17:24 -0000 1.158 > +++ sys_pipe.c 10 Nov 2003 17:21:47 -0000 > @@ -331,5 +331,5 @@ > if (error != KERN_SUCCESS) { > if (ppsratecheck(&lastfail, &curfail, 1)) > - printf("kern.maxpipekva exceeded, please see tuning(7).\n"); > + printf("kern.ipc.maxpipekva exceeded; see tuning(7)\n"); > return (ENOMEM); > } > %%% > > > And tuning(7) doesn't mention this, either. > > > > Is this just work-in-progress, or did someone forget to commit something? > > Seems like tuning pipe kva is completely absent in tuning(7) (so the above > message can be shortened further). You can tune kva generally as documented > there, but the pipe limit is separate. > > > PS: Lesson of the day: no pipe KVA, no su. Great fun on remote > > machines! :-) > > It's interesting that su was the point of failure. It uses a pipe hack > for IPC. Otherwise it doesn't use pipes, at least direectly. It > shouldn't need to use the pipe hack. My version uses signals instead.