Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <011f01c25c9e$189b6320$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad.Scott@dsl.pipex.com>
To: "Nicholas Wourms" <nwourms@yahoo.com>
Cc: <cygwin@cygwin.com>
References: <20020915034506.70059.qmail@web21006.mail.yahoo.com>
Subject: Re: Curious behavior of CYGSERVER
Date: Sun, 15 Sep 2002 10:56:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

"Nicholas Wourms" <nwourms@yahoo.com> wrote:
>
> --- Robert Collins <rbcollins@cygwin.com> wrote:
> >
> > On Sun, 2002-09-15 at 11:43, David A. Cobb wrote:
> > >
> > > What is really bad is that somehow, having CYGSERVER involved
> > defeats
> > > the stdout redirection.  For example, the make check not only ran
> > for 13
> > > hours, but it also gave me very little clue as to its success or
> > failure.
> >
> > That is very unexpected. The HEAD code for cygserver supported
> > normal
> > and tty operation without any regressions from having cygserver not
> > running, when I merged it.
> >
> > Are you sure that that is the cause?
>
> I can actually confirm this behavior since I started testing it a few
> months ago.  Always seems to be the most predominant when running
> configure scripts and the like.  Conrad has some theories on why this
> may be happening, so I'll let him have his say.

It's likely my failing memory cells, but I can't remember any discussion
of this sort of behaviour.  There've been various configure script
issues but none really due to cygserver (it just helped to tickle other
issues) and none outstanding that I knew of.  Could you refresh my
memory, Nicholas?

// Conrad


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/