Tech Insider					     Technology and Trends

			      USENET Archives

Newsgroups: comp.os.linux.development
Subject: suggestion for IPC feature/bugfix
Date: 5 Apr 1994 11:35:55 GMT
Organization: North Carolina State University, Project Eos
Lines: 28
Distribution: world
Message-ID: <2nrier$>
Keywords: IPC

Hello Linuxers,
     I have recently begun learning about SYSV IPC on my linux machine.  One
thing I discovered is that if you allocate shared memory it stays allocated
even after the program exits unless you mark it for deletion (yes, I know
it says this in the man page).  I understand
that this is a feature because it allows processes to communicate through
shared memory even if they are not running at the same time.  The problem
I found is that if you create using the IPC_PRIVATE flag, and do not mark
it for deletion, it still exists when the program terminates, and I do not
think you can get rid of it.  This bothers me because it is a way for a user
to effectivly bring down a linux machine, and the only cure that I can find
is to reboot the machine.  What I would like to prepose is this.  Create a
/proc/shared directory.  In this directory there would be a file corrosponding
to every shared memory segment.  The program using shared memory would 
effectivly have this file open.  When the segment was marked for deletion this
file would be deleated, but programs could still access the memory, just like
programs can still access files which have been deleted if they already have
them open.  When all the files using that shared memory exited, the shared
memory would be lost.  However, if a programmer forgot to delete a shared
memory segment, it would still exist in /proc/shared, and could be deleted
using the rm command.  Prehaps it would even be possible to implement shared
memory by mmaping this file?  Anyway, I just wanted to toss this idea out.
Prehaps there is already a way to accomplish what I want to do?

Thanks for listening,

Jim Nance

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO v IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or

Electronic mail:			       WorldWideWeb: