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
From:	"Robert Collins" <robert DOT collins AT syncretize DOT net>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	RE: changes to fhandler_process.cc from 02/06/2002 should be reverted
Date:	Mon, 1 Jul 2002 08:45:05 +1000
Message-ID:	<000801c22087$c8462830$0200a8c0@lifelesswks>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-MIMEOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Importance:	Normal
In-Reply-To:	<20020630223718.GA3808@redhat.com>

> -----Original Message-----
> From: cygwin-developers-owner AT cygwin DOT com 
> [mailto:cygwin-developers-owner AT cygwin DOT com] On Behalf Of 
> Christopher Faylor
> Sent: Monday, 1 July 2002 8:37 AM

> Ok, but you can't keep the shared memory for every process 
> open for the
> duration of the life of a fhandler_process.  I don't know how 
> to deal with
> this but using up lots of resources isn't the way to do it.

This sounds like something that the cygserver could help with. I.e. if
the cygserver isn't running, accept some inaccuracy, or large resource
usage, and if it is running, just query it.

Just a thought,
Rob

- Raw text -