This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: echo "$(echo '\r')" oddity
- From: Brian Dessent <brian at dessent dot net>
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Mon, 09 May 2005 03:06:22 -0700
- Subject: Re: echo "$(echo '\r')" oddity
- References: <D1D50F9C5151D2119FF000104BB3F9B708E1B75B@NL-ROT-MAIL02>
- Reply-to: cygwin at cygwin dot com
Jan Just Keijser wrote:
> in interactive mode the command seems to work fine. What happens if you
> build socat and then run the test script (./test.sh) ? Which tests does it
> fail on?
test.sh fails on the openssl test for me too. I can't really follow
exactly what the testcase is doing though. It looks like there's a race
condition somewhere because you get the previous command's output with
each command:
$ socat -t0.1 exec:'openssl s_server -accept 12009 -quiet -cert
cacert.pem -key privkey.pem' pipe &
$ echo -n "1" | socat -t0.1 -
openssl:localhost:12009,cafile=cacert.pem,verify=1
$ echo -n "2" | socat -t0.1 -
openssl:localhost:12009,cafile=cacert.pem,verify=1
1
$ echo -n "3" | socat -t0.1 -
openssl:localhost:12009,cafile=cacert.pem,verify=1
2
$ echo -n "4" | socat -t0.1 -
openssl:localhost:12009,cafile=cacert.pem,verify=1
3
I don't know what's going there. You'd probably have to delve into an
strace to find out.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/