From owner-freebsd-stable@FreeBSD.ORG Mon Mar 29 14:26:23 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE06316A4CE for ; Mon, 29 Mar 2004 14:26:23 -0800 (PST) Received: from util.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FA2F43D3F for ; Mon, 29 Mar 2004 14:26:23 -0800 (PST) (envelope-from spork@inch.com) Received: from shell.inch.com (www.inch.com [216.223.192.20]) i2TMQMoC051387 for ; Mon, 29 Mar 2004 17:26:22 -0500 (EST) (envelope-from spork@inch.com) Received: from shell.inch.com (localhost [127.0.0.1]) by shell.inch.com (8.12.8p2/8.12.8) with ESMTP id i2TMQMVG088049 for ; Mon, 29 Mar 2004 17:26:22 -0500 (EST) (envelope-from spork@inch.com) Received: from localhost (spork@localhost)i2TMQMXC088046 for ; Mon, 29 Mar 2004 17:26:22 -0500 (EST) X-Authentication-Warning: shell.inch.com: spork owned process doing -bs Date: Mon, 29 Mar 2004 17:26:22 -0500 (EST) From: Charles Sprickman To: freebsd-stable@freebsd.org Message-ID: <20040329172225.C78570@shell.inch.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: SHMMAX in kernel config X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 22:26:23 -0000 Howdy, I recently upgraded an old box running 4.6.2 to 4.9-p4, and found that afterwords, Postgres was hanging due to kern.ipc.shmmax being way too low (4096 bytes, or one page). The line in the kernel config (as confirmed by LINT) was this: options SHMMAXPGS=8192 # max amount of shared memory pages (4k) options SHMALL="(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)" Thinking perhaps this was no longer valid, I tried again by doing the math myself, but I got the same result; kern.ipc.shmmax=4096. For now I'm just setting this in sysctl.conf, but I'm curious as to what has changed, or what I'm doing wrong. Thanks, Charles -- Charles Sprickman spork@inch.com