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
Message-ID: <03ee01c212e8$fe384b50$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: "Robert Collins" <robert DOT collins AT syncretize DOT net>
Cc: <cygwin-developers AT cygwin DOT com>
References: <009d01c212e5$e0804a70$0200a8c0 AT lifelesswks>
Subject: Re: System-wide mutexes and pthreads
Date: Thu, 13 Jun 2002 15:45:41 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Robert Collins" <robert DOT collins AT syncretize DOT net> wrote:
> > Conrad Scott wrote:
> > More pertinently we should think about making sure that at
> > least some things
> > work if the daemon is killed and re-started while there are
> > cygwin programs
> > running. But I don't think that's an immediate concern.
>
> This is orthogonal: whether cygserver uses cygwin1.dll or not, killing
> cygserver will affect all other cygwin process in the same fashion.

Agreed. I was thinking that it's more of an issue than whether cygserver
should be a cygwin process or not. But it's not an immediate issue.

// Conrad