Date: Fri, 12 Dec 2003 18:28:03 +0300 From: "Artem 'Zazoobr' Ignatjev" <timon@memphis.mephi.ru> To: "Christoph P. Kukulies" <kuku@kukulies.org> Cc: freebsd-current@freebsd.org Subject: Re: gimp fails suddenly Message-ID: <1071242883.735.24.camel@timon.nist> In-Reply-To: <20031212143609.GA20325@gilberto.physik.rwth-aachen.de> References: <200312070945.hB79jKds039814@www.kukulies.org> <1071238350.735.3.camel@timon.nist> <20031212143609.GA20325@gilberto.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12.12.2003, at 17:36, Christoph P. Kukulies wrote: > On Fri, Dec 12, 2003 at 05:12:31PM +0300, Artem 'Zazoobr' Ignatjev wrote: > > I've found following advise after installing vmware3 port... > > That revived gimp back for me: > > > > sysctl -w kern.ipc.shm_allow_removed=1 > > > > I've put it into sysctl.conf, and run with it. > > That's fine. Just tell me, what does this actually mean? Is it practically > the same as running gimp --no-shm ? Or is shm activated (like a module being > not present and the getting loaded?). I think it's being activated... Dunno, it works for me - I pray for it (: quick grep thru kernel sources shows that without this kernel will return NULL for shared memory in some cases -- Artem 'Zazoobr' Ignatjev <timon@memphis.mephi.ru>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1071242883.735.24.camel>