From owner-freebsd-stable@FreeBSD.ORG Mon Oct 8 14:34:08 2007 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D440E16A418 for ; Mon, 8 Oct 2007 14:34:08 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 3A1B413C46E for ; Mon, 8 Oct 2007 14:34:07 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id l98EWhoO011409; Mon, 8 Oct 2007 16:32:49 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id l98EWcsT011408; Mon, 8 Oct 2007 16:32:38 +0200 (CEST) (envelope-from olli) Date: Mon, 8 Oct 2007 16:32:38 +0200 (CEST) Message-Id: <200710081432.l98EWcsT011408@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, tpresence@hotmail.com In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 08 Oct 2007 16:32:51 +0200 (CEST) Cc: Subject: Re: freebsd ipsc -a output missing X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, tpresence@hotmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2007 14:34:08 -0000 The Presence wrote: > I have a generic kernel on my FreeBSD 6.2 system, and I am getting > errors regarding PMAP_SHPGPERPROC which is set at 201 (default). The default value is 200. > Because the system is a heavy load websever, this happens quite > often. I want to calculate the proper value to to it to, but my ipcs > software isn't working. Anyone know how to reconcile it? It has nothing to do with ipcs. The ipcs tool is used to report SysV IPC data. I suggest you try increasing PMAP_SHPGPERPROC in your kernel config, or adjust the vm.pmap.shpgperproc loader tunable (same effect, but doesn't require building a new kernel). > I do have: > > options SYSVSHM # SYSV-style pscshared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > > compiled into the kernel. Irrelevant. > Output from ipcs -a: > > mercury# ipcs -a > Message Queues: > T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME > > Shared Memory: > T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME > > Semaphores: > T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME Obviously nothing on your machine uses SysV IPC, so all fields are empty. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "When your hammer is C++, everything begins to look like a thumb." -- Steve Haflich, in comp.lang.c++