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:	<00f001c25f4b$6a01bd40$6132bc3e@BABEL>
From:	"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To:	<cygwin-developers AT cygwin DOT com>
Subject:	cygserver merge
Date:	Wed, 18 Sep 2002 20:41:30 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

I know there's a new cygwin release looming ahead of us and I wondered
if this would be a good moment to merge the current cygserver code into
the mainline?  The main reason for this would be to get hold of the
change whereby the server removes its socket file on exit as this seems
to creating more noise on the list than is required.

The current state of the cygwin_daemon branch is that the exposed
functionality is little different from the state it was in when I took
it over: most of my effort has gone into more generic issues with the
existing code and re-arranging a few bits.  I have some of a semaphore
implementation sitting in my sandbox here at home but it'll be a while
before that gets anywhere (I'm going rather slowly recently).

The code is in daily use by myself and by (at least) Nicholas (and that
covers both win 9x and win2k AFAIK).  And since the shm entry points
will still be missing, there shouldn't be too much scope for problems.

Any votes either way?

// Conrad

- Raw text -