Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: Re: Curious behavior of CYGSERVER
From: Robert Collins <rbcollins AT cygwin DOT com>
To: Cygwin Discussion <cygwin AT cygwin DOT com>
In-Reply-To: <3D83E5C6.90102@cox.net>
References: <3D83E5C6 DOT 90102 AT cox DOT net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-MARVx2GZg2kQN2i3sZKO"
Date: 15 Sep 2002 12:11:00 +1000
Message-Id: <1032055860.7167.36.camel@lifelesswks>
Mime-Version: 1.0

--=-MARVx2GZg2kQN2i3sZKO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2002-09-15 at 11:43, David A. Cobb wrote:
> I discussed above (http://cygwin.com/ml/cygwin/2002-09/msg00302.html) my
> problems attempting to do a bootstrap of gcc-3.2.   One experiment
> involved firing up CYGSERVER.  As mentioned in the previous thread, the
> program went much much much further this way -- make check took about 13
> hours!
>=20
> In the process, I notice two unexpected behaviors.  The CYGSERVER emits
> dots (.) on the screen every little while - perhaps it emits one
> everytime it gets called.  This isn't bad -- it makes a handy pulse to
> be sure the machine hasn't just frozen up.  Three screenshots are
> attached fro the make  check run.

Thats what it is, simply some feedback. When cygserver starts to provide
significant functionality, that may get removed. Or at least that was my
plan before I handed it over to Conrad.
=20
> 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?

Rob

--=-MARVx2GZg2kQN2i3sZKO
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9g+wzI5+kQ8LJcoIRAhhmAJ4ulh2znmAxUBewFwghni9XpVqu5gCffJlH
IV84GqPABWfaHoX/J+xJT/8=
=fvWZ
-----END PGP SIGNATURE-----

--=-MARVx2GZg2kQN2i3sZKO--