Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID:	<3B05492C.1080402@ece.gatech.edu>
Date:	Fri, 18 May 2001 12:09:17 -0400
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20010131 Netscape6/6.01
X-Accept-Language:	en
MIME-Version:	1.0
To:	Fred Yankowski <fred AT ontosys DOT com>
CC:	Corinna Vinschen <cygwin-apps AT cygwin DOT com>
Subject:	Re: Updated: cygrunsrv-0.92-2
References:	<20010517161408 DOT A60686 AT enteract DOT com> <20010518101617 DOT B31266 AT cygbert DOT vinschen DOT de> <20010518103001 DOT A61059 AT enteract DOT com>

Fred Yankowski wrote:

> 
> I agree.  We should be able to support the NT-service-management code
> in just one place -- cygrunsrv -- rather than duplicating in each
> separate service.  OTOH, some simple services such as ipc-daemon can
> run as a single NT process when service-management is integrated into
> them. 
Well, eventually IPC services will be supported by cygwin itself, 
coupled with a "cygwin daemon".  THAT daemon should use cygrunsrv. 
CygIPC (and ipc-daemon) are just interim solutions...
--Chuck

- Raw text -