From owner-freebsd-current Tue Jun 6 5:53:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id D16D437B665 for ; Tue, 6 Jun 2000 05:53:12 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id PAA29510; Tue, 6 Jun 2000 15:51:56 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id PAA54626; Tue, 6 Jun 2000 15:32:32 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <393CEF53.EAC2041C@FreeBSD.org> Date: Tue, 06 Jun 2000 15:32:19 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Alexander Sanda Cc: current@FreeBSD.org Subject: Re: Shared memory changes in current? References: <4.3.2.7.2.20000604012146.02c204a8@mail.kabsi.at> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Sanda wrote: > Anyone aware of them? > > After building a complete kernel + world with a very recent -current > (Saturday morning, european time) I now get lots of shared memory errors > in gnome (most coming from gdk and imlib, some from Xfree 4 aswell). I > recompiled parts of gnome (gtk+, imlib, glib) and the situation has > slightly changed, but gdk still throws a lot of shmget() failed: errors. It has noting to do with kernel/gnome. XFree 4.0 is known to be very hungry for the shared memory, so you should increase SHMSEG parameter in your kernel config file. There are no guidelines as to what exact number will be sufficient, so you should define it in experimental way. I personally set it to 100 (options SHMSEG=100) and do not see any warnings anymore. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message