Date: Sun, 31 May 1998 20:45:05 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: hasty@rah.star-gate.com (Amancio Hasty) Cc: tlambert@primenet.com, mike@smith.net.au, rminnich@Sarnoff.COM, doconnor@gsoft.com.au, hackers@FreeBSD.ORG Subject: Re: Star Office Installation Message-ID: <199805312045.NAA12554@usr06.primenet.com> In-Reply-To: <199805310942.CAA20634@rah.star-gate.com> from "Amancio Hasty" at May 31, 98 02:42:44 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > My next question is , > > > why so many postings about Star Office without a single soul venturing > > > into the linux layer to solve at least the ipc shared memory segments > > > clean up? > > > > > > Well, lets chat about it some more 8) > > > > By definition, shared memory segments are persistant. > > > > It would be an error to delete them when the last reference is deleted. > > > > This is arguably a design flaw, but being a design flag, there's really > > nothing you can do about it. > > Well, I guess on Linux star office misbehaves by deleting its ipc > shared data segments when it exits. No, it doesn't. But if FreeBSD deleted them on it behalf when Star Office exited, FreeBSD would be in error. > Most likely whats going is that we are not handling properly the ipc > calls or possibly something else which is causing Star Office not > to delete the ipc shared data segments upon exit. You mean "shutdown", not "exit". My point was that SysV IPC is not resource tracked, and it would be an error for FreeBSD to resource track it (which is what was being requested). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805312045.NAA12554>