From owner-freebsd-questions Mon Sep 28 20:44:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29687 for freebsd-questions-outgoing; Mon, 28 Sep 1998 20:44:02 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from kakapo.pinnacle.co.nz (pinsoft.internet.co.nz [202.37.141.181]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29648 for ; Mon, 28 Sep 1998 20:43:59 -0700 (PDT) (envelope-from jonc@pinnacle.co.nz) Received: from tui.pinnacle.co.nz (tui.pinnacle.co.nz [202.37.163.3]) by kakapo.pinnacle.co.nz (8.8.8/8.8.8) with SMTP id PAA17620; Tue, 29 Sep 1998 15:38:02 +1200 (NZST) (envelope-from jonc@pinnacle.co.nz) Date: Tue, 29 Sep 1998 15:38:01 +1200 From: Jonathan Chen To: Purrcat cc: questions@FreeBSD.ORG Subject: Re: shared mem between parent & child In-Reply-To: <361036B3.FCE6DA8F@uci.kun.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Sep 1998, Purrcat wrote: > I think I can do this with a shared variable (if > this kind of thing exists anyway).. If there's no such thing as a > 'shared variable', could it be done in another way (like stdin and > stdout or something?) There's the shmat(2) and friends. You could also do this using pipes or sockets from parent to children. -- Jonathan Chen Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message