Message-ID: <4F08B185.7050709@dancol.org>
Date: Sat, 07 Jan 2012 12:56:37 -0800
From: Daniel Colascione <dancol@dancol.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Does Cygwin Terminal queue output to stdout?
References: <CAAJ38WVH3UEqBOj9kBVh5PeMnXs9evWxJ5uSK77xJxOyd13XRg@mail.gmail.com>
In-Reply-To: <CAAJ38WVH3UEqBOj9kBVh5PeMnXs9evWxJ5uSK77xJxOyd13XRg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2E3A5FAC7A198B59E460B8FD"
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

--------------enig2E3A5FAC7A198B59E460B8FD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 1/7/12 12:49 PM, inetjunkmail wrote:
> First a quick aside to say thank you for Cygwin Terminal.  I can't
> articulate how nice it is to be freed of cmd.exe!

You were always free of cmd.exe, which is akin to bash. Now you're
also free of conhost, the closest thing windows has to a terminal
emulator.

> I have installed windump (http://www.winpcap.org/windump/) and tshark
> which is part of the WireShark package
> (http://www.wireshark.org/download.html) both of which leverage
> WinPCAP libraries (http://www.winpcap.org/).
>=20
> When I run tshark or windump in a cmd.exe window (e.g. "tshark -i1
> -n") I see immediate output of network traffic seen by my network
> interface and continues to stream live network traffic information.
>=20
> When I run either program in Cygwin Terminal, there is about a 20
> second delay before I see any output.  At which time it immediately
> dumps the previous 20 seconds of "queued up" output and hangs again
> for 15-20 seconds, followed by another dump of "queued up" output,
> etc...
>=20
> Is there some way I can have Cygwin Terminal stream the data like cmd.exe=
 does?

=46rom the point of view of these programs, mintty is a pipe. When a
program thinks it's writing to a display (a tty), it typically flushes
the output after every line. But when a program thinks the user won't
see its output, a program typically flushes its buffers less often
because writing in larger chunks is more efficient. You need to
convince these non-Cygwin programs to not buffer their output. Have
you tried the conin utility?

https://code.google.com/p/mintty/source/browse/utils/conin.c


--------------enig2E3A5FAC7A198B59E460B8FD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk8IsYoACgkQ17c2LVA10Vs99ACeL6tcly3DpIlOE9L5v0vyUXai
wfQAnifqYNvu11c9f96OUOOJer194/XZ
=jTUo
-----END PGP SIGNATURE-----

--------------enig2E3A5FAC7A198B59E460B8FD--