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/
