bin/176713: [patch] nc(1) closes network socket too soon
Adrian Chadd
adrian at freebsd.org
Mon Jul 22 07:28:06 UTC 2013
Right. Yes, I had a typo. I meant that it shouldn't die on seeing a
read EOF after closing the write side of the socket.
So, what you're saying is:
* nc sees EOF on stdin
* nc decides to abort before seeing the rest of the data come in from
the remote socket (and then trying to write it, and aborting if it
sees EOF on stdin _and_ EOF/error on writing to stdout)
Right?
-adrian
More information about the freebsd-hackers
mailing list