Date: Wed, 1 Mar 2000 11:28:13 -0800 (PST) From: John Polstra <jdp@polstra.com> To: chris@netmonger.net Cc: current@freebsd.org Subject: Re: Shared memory - Was: 2 Queries Message-ID: <200003011928.LAA75785@vashon.polstra.com> In-Reply-To: <20000301124613.A15018@netmonger.net> References: <20000229021327.E21720@fw.wintelcom.net> <20000229134143.B4903@netmonger.net> <20000301182028.C61034@plab.ku.dk> <20000301124613.A15018@netmonger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20000301124613.A15018@netmonger.net>, Christopher Masto <chris@netmonger.net> wrote: > On Wed, Mar 01, 2000 at 06:20:28PM +0100, Anton Berezin wrote: > > I would say that the programs you've mentioned are badly written then. > > > > It takes no more than > > > > XSync(disp,False); > > shmctl( shmid, IPC_RMID, 0); > > It takes no more than a well-designed operating system service to > ensure that badly written programs don't fail to release resources > when they crash. We didn't design that particular service. That's why it's called System V shared memory. Also, it's persistent for legitimate design reasons, just like files are. Applications need to clean up after themselves. The OS has no way of knowing whether an application wants its shared memory segments to survive after it terminates. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003011928.LAA75785>