From owner-freebsd-stable Fri May 4 11:47:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 7D0A837B423 for ; Fri, 4 May 2001 11:47:54 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f44IlMl30759; Fri, 4 May 2001 11:47:22 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 May 2001 11:47:22 -0700 (PDT) From: Matt Dillon Message-Id: <200105041847.f44IlMl30759@earth.backplane.com> To: lists@mediumgreen.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Should /sys/i386/conf/GENERIC's SysV shared memory settings+defaults be re-thought? References: <200105041729.f44HTjr27074@earth.backplane.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> whether I have to raise SHMMNI and SHMSEG even higher -- I'm guessing :> that your problems were mostly due to the too-low SHMMAXPGS default. : :I've seen similar issues with my home machine. If I leave vmware running, :my backups fail. I haven't yet gotten around to rebuilding the kernel with :the shm setting changed. : :Here is my current ipcs output: : :... Thanks guys. As I thought.. the issue is almost certainly the shared memory maximum. I've raised the default from 4M to 32M in -current and I will MFC it to -stable on monday. I also raised the control structure limits slightly. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message