From owner-freebsd-current Tue Feb 29 12:15:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 2974837BC0A for ; Tue, 29 Feb 2000 12:15:15 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id PAA12217; Tue, 29 Feb 2000 15:15:05 -0500 (EST) Message-ID: <20000229151505.A12016@netmonger.net> Date: Tue, 29 Feb 2000 15:15:05 -0500 From: Christopher Masto To: Cliff Rowley Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: Shared memory - Was: 2 Queries Mail-Followup-To: Cliff Rowley , Alfred Perlstein , freebsd-current@FreeBSD.ORG References: <20000229134143.B4903@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Cliff Rowley on Tue, Feb 29, 2000 at 08:08:45PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 29, 2000 at 08:08:45PM +0000, Cliff Rowley wrote: > It'd be nice if we had a utility that could clean out and reclaim the > shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and > obviously any other apps using shared memory), and get on with life :) Uh.. ipcrm? The problem is that I always end up taking something out that's in use.. or intentionally left around unattached, so it just _looks_ like it's not in use. I think imlib does this as some sort of cache (ugh!). Then I experience a variety of even more annoying random behavior. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message