Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!pasteur!ucbvax!hplabs!sdcrdcf!ism780c!mikep
From: mikep@ism780c.UUCP (Michael A. Petonic)
Newsgroups: comp.unix.wizards
Subject: Shared Memory in BSD4.3 is lacking?
Message-ID: <9100@ism780c.UUCP>
Date: 19 Feb 88 10:45:44 GMT
Reply-To: mikep@ism780c.UUCP (Michael A. Petonic)
Organization: Interactive Systems Corp., Santa Monica CA
Lines: 32


Now, don't get me wrong.  I like Berzerkeley and all, but JEEZ!  No
shared memory?  After implimenting a program to use shared memory in
BSD (from the specs in the "Berkeley Software Architecture Manual (4.3
edition)") and trying to compile it, I notied I'm missing some
functions.  So, I look really really really close at the page and
there is a footnote that in effect say "We don't have any of these
functions implemented, yet."

What gives?  After trying various methods to communicate information
accross the parent-child barrier, I am convinced that shared memory is
the only way to go.

Can someone more familiar with BSD give me a hand?  Is there
a crufty trick I can use with sockets to have *fast* interprocess
communication?  

What I'd really like to do is to share a file pointer (that's
right, a file pointer, not a file descriptor) accross processes
along with several variables.  Any decent ways out there?

-MikeP
--------
Michael A. Petonic                      (213) 453-8649 x3247
INTERACTIVE Systems Corporation         "My opinions in no way influences
2401 Colorado Blvd.                     the price of tea in China."
Santa Monica, CA. 90404
{sdcrdcf|attunix|microsoft|sfmin}!ism780c!mikep

additional disclaimer:  I'm a System V man out of necessity, so
no "What!?!?!  You don't know every detail of sockets and
datagrams???" type flames, please.