From owner-freebsd-stable Thu May 3 12: 1:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id C521D37B422 for ; Thu, 3 May 2001 12:01:37 -0700 (PDT) (envelope-from jmcoopr@webmail.bmi.net) Received: from webmail.bmi.net (dsl-154.bmi.net [207.173.60.230]) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id MAA13643 for ; Thu, 3 May 2001 12:01:35 -0700 Message-ID: <3AF1AB14.872CBA2A@webmail.bmi.net> Date: Thu, 03 May 2001 12:01:40 -0700 From: John Merryweather Cooper Reply-To: FreeBSD-STABLE Mailing List X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en, en-GB MIME-Version: 1.0 To: FreeBSD-STABLE Mailing List Subject: Should /sys/i386/conf/GENERIC's SysV shared memory settings defaults be re-thought? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After finally getting Amanda up and running on my system, I noticed that my cron jobs for amdump would crash with an error in SHMGET if X was running when the amdump job was scheduled. I have also been plagued by IMLIB SHM memory allocation errors. I have just discovered that, by increasing the defaults for all the SysV settings listed in LINT, I have been able to make all those errors disappear; and Amanda will now run to completion even with X running. I increased all these settings by about a factor of x8--remembering that in OS/2 half of all physical memory was made available for shared memory operations--giving me 32 megs of shared memory. In light of the fairly common use of X, should: 1) a commented out section in generic be included with suggested settings that would work better with X, Amanda, and the like; 2) a separate XGENERIC config file optimized for X users; or 3) modify GENERIC to have these increased settings by default (nice for people who run X with GENERIC kernels). Thoughts? jmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message