DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=whnAjSW+6KsuZpkvXErGmFkDJ9SYG
	pA9I1K2j5usxqep7v/tzqByB6P6ug3BLUhk1EZxldadJlznZIgkSFXp1/z78bXEe
	WZQX9YqWFk5j3XFwXvNsWbzL8mVVyK29XVtWqwsdZSKta+pqC2+5RPKxqIh/9iB5
	gC2k+aYDrLqJ0M=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: =?UTF-8?Q?David_Bala=C5=BEic?= <xerces9@gmail.com>
Date: Sun, 22 Jan 2017 21:19:20 +0100
Message-ID: <CAPJ9Yc9BJXrvrFz3pKQiEzzQ8a8f0_9rPuLn+o+mc5_Zo2wdmg@mail.gmail.com>
Subject: Pipe behavior clarification?
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

Hi!

Is this a correct pipe behavior?

$ echo booo | tee >(md5sum --tag) >/dev/null
MD5 (-) = 9c8b79bdf79ef0ee73a77b8d36d27a2d

$ echo booo | tee >(md5sum --tag) | cat >/dev/null

It surprised me, that the output of md5sum is dealed the same way as
the std output of tee in the second case, but separately in the first
case.

Using cygwin 64 bit (up to date), with bash.

Regards,
David

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple