Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 4 Jan 2002 11:38:34 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Daemon (again) Message-ID: <20020104163834.GD29367@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <0d3101c194ee$48d9dfd0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0d3101c194ee$48d9dfd0$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Fri, Jan 04, 2002 at 06:06:07PM +1100, Robert Collins wrote: >----- Original Message ----- >From: "Gary R. Van Sickle" >> You can, and I will, but I think I should address this security issue >with mutt >> first and reroll it. Hopefully I can get that done yet tonight, but >you know >> how things go.... > >For sure :}. > >> What exactly would you like me and others to test/evaluate? From your >post >> previous to the above: >> >> "Also the code is in two distinct chunks: >> 1) A daemon to run under NT and 9x and provide cross-process services >to >> cygwin. > >Does this chunk look like a reasonable implementation. Does cygwin start >playing up/die badly. Are there any significant issues that *you* think >would stop the release of (say) cygwin 1.7 with the daemon as-is. My biggest issue is "Does cygwin run fine *without* the daemon?" That's the big one. The reason for this is that we don't want to tell our customers that they have to install a cygwin daemon just to compile their programs. AFAIK, the daemon is not going to provide any functionality that will improve things like gcc or gdb so it has to be as unobtrusive as possible. cgf