Date: Mon, 23 Apr 2001 01:45:51 -0500 From: Andrew Hesford <ajh3@chmod.ath.cx> To: David Petrou <dpetrou@cs.cmu.edu> Cc: freebsd-stable@freebsd.org Subject: Re: shared mem default limits Message-ID: <20010423014551.A94798@cec.wustl.edu> In-Reply-To: <20010423022135.A48878@amant.pdl.cs.cmu.edu>; from dpetrou@cs.cmu.edu on Mon, Apr 23, 2001 at 02:21:35AM -0400 References: <20010423022135.A48878@amant.pdl.cs.cmu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 23, 2001 at 02:21:35AM -0400, David Petrou wrote: > Hi. I used to get a lot of errors concerning shared memory segments > not being available. After doing some googling, I found the magic > answer to my gnome woes. It turns out that running Enlightenment, > gnome, and lots of windows quickly exhausts the default kernel limits > on some shared mem parameters. > > This problem was discussed in -current in June 2000. > > After throwing in: > > options SHMMAXPGS=8192 > options SHMMNI=4096 > options SHMSEG=1024 > > my problems went away. (Problems would manifest themselves as windows > disappearing when starting new apps, etc.) > > Perhaps we could up the defaults? Is there a compelling reason on > today's machines to keep them small? > > david Is that the solution? I've been having a similar problem. In an attempt to solve the problem, I tried deleting shared memory segments, and I got this error with certain values: % ipcrm -m 65543 ipcrm: shmid(65543): : Invalid argument I know the segment exists, I can see it in ipcs. Also, I own it. How can I forcefully delete those segments which just don't die? -- Andrew Hesford ajh3@chmod.ath.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010423014551.A94798>