From owner-freebsd-current Sun Aug 11 14:11:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13375 for current-outgoing; Sun, 11 Aug 1996 14:11:50 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (root@wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA13366 for ; Sun, 11 Aug 1996 14:11:42 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id QAA03860; Sun, 11 Aug 1996 16:26:58 -0400 (EDT) Date: Sun, 11 Aug 1996 16:26:57 -0400 (EDT) From: Gary Roberts To: Terry Lambert cc: freebsd-current@freebsd.org Subject: Re: your mail In-Reply-To: <199608112015.NAA24046@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 11 Aug 1996, Terry Lambert wrote: > > Is it possible to 'clean the shared memory pool'? > > > > On running some programs(Mainly linux apps) I get errors that there is no > > shared memory available. Of course the program runs fine 2 or 3 times, > > but after that, well, I have to reboot :( > > 1) The programs should remove the shared memory segment when they > exit. This is not a resource tracked by _exit (for obvious > reasons: if process A and process B and process C share a > segment, and C exits, you don't want to screw A & B). > > 2) If you can't fix the software to use the interfaces in the > way they are documented as being required to be used, then > you should: > > man ipcrm > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > Right. But they aren't cleaning the memory. So I have to run ipcrm each time. Which is ok. It's not a big deal ... Thanks for all the responses, I got it fixed... sorta =) Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages ------------------------------------------------------------------------------ This email message is copyrighted and is not allowed to be duplicated, reproduced, or even seen on the MSN, AOL, or the Compuserve computer networks.