From owner-freebsd-stable Thu May 3 12:13:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id B223B37B424 for ; Thu, 3 May 2001 12:13:54 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f43JDsu01446 for ; Thu, 3 May 2001 12:13:54 -0700 (PDT) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma001442; Thu, 3 May 2001 12:13:45 -0700 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f43JDjw72049 for freebsd-stable@FreeBSD.ORG; Thu, 3 May 2001 12:13:45 -0700 (PDT) Date: Thu, 3 May 2001 12:13:45 -0700 (PDT) From: David Wolfskill Message-Id: <200105031913.f43JDjw72049@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: Should /sys/i386/conf/GENERIC's SysV shared memory settings defaults be re-thought? In-Reply-To: <3AF1AB14.872CBA2A@webmail.bmi.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 03 May 2001 12:01:40 -0700 >From: John Merryweather Cooper >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. Hmmm.... >... >Thoughts? I find this somewhat surprising, since I've been backing up not only the servers here, but also the important desktops (the ones running FreeBSD) on engineers' desks here for around 2.5 years using amanda. And the engineers generally run X... but I've never encountered that problem. (Before the shared memory stuff was included in GENERIC, I included it manually in the kernels when I set up their machines. I just left the default settings alone.) I suppose it may depend on the particular X workload; for example, I use tvtwm as a window manager, while I understand that some folks prefer the appearance or behavior of a window manager that is a bit more resource- intensive. I do tend to kick "maxusers" up a bit; I have it set to 128 on my laptop. I haven't checked to see if that affects such things as shared memory availability.... (I also tend to be fairly generous with swap space: I prefer to avoid swapping, but if the system really needs to swap, I much prefer letting it do so to preventing that.) Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message