Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
content-class:	urn:content-classes:message
Subject:	RE: Two fixup routines in fork_child seem misplaced (Corinna, Robert)
MIME-Version:	1.0
Date:	Mon, 25 Mar 2002 10:34:38 +1100
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
Message-ID:	<FC169E059D1A0442A04C40F86D9BA76008AB8A@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g2ONYfC15874

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Monday, March 25, 2002 8:23 AM

> There is obviously no shm usage these days.  I didn't look 
> closely enough to see if the regions that are being mapped 
> are coming from the parent.  Maybe they're just coming from 
> the server, now that I think about it.  That would make more sense.

IIRC (I'm 75% through a PC rebuild) the shm doesn't need any data from
the parent. All it does it walk the local cache of shm entries, and
syncronise with the server for required handles. I will check in the
next day or two however.

Rob

- Raw text -