From owner-freebsd-hackers Tue Feb 3 23:17:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03393 for hackers-outgoing; Tue, 3 Feb 1998 23:17:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03377 for ; Tue, 3 Feb 1998 23:17:44 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id RAA07706; Wed, 4 Feb 1998 17:47:15 +1030 (CST) Message-Id: <199802040717.RAA07706@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Schuster cc: "hackers@FreeBSD.ORG" Subject: Re: Shared memory and signals In-reply-to: Your message of "Wed, 04 Feb 1998 08:06:23 BST." <34D8136F.CF845A68@utimaco.co.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Feb 1998 17:47:15 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" > You probably wouldn't want to do that, since shmctl(IPC_RMID,..) really > removes the shm segment, and other processes trying to use it wouldn't > be very happy about that ... > You could find out about the number of attached processes/threads using > something like: Hmm, yes but I know of at least one program (paradise netrek :) which uses the fact that the shared mem segment is persistent... --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | ---------------------------------------------------------------------