Date: Mon, 22 Jul 2013 00:28:04 -0700 From: Adrian Chadd <adrian@freebsd.org> To: "Ronald F. Guilmette" <rfg@tristatelogic.com> Cc: freebsd-hackers@freebsd.org Subject: Re: bin/176713: [patch] nc(1) closes network socket too soon Message-ID: <CAJ-VmokAhE%2Buy4-3QAW6mK__sgw%2BL2_Y6M29O_%2BX%2BAk5hoaW6Q@mail.gmail.com> In-Reply-To: <94798.1374462380@server1.tristatelogic.com> References: <CAJ-VmonDfzG7H1pPOxt%2BPTpdigrzuGe8di8zhoUsLGi3cGZAXA@mail.gmail.com> <94798.1374462380@server1.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokAhE%2Buy4-3QAW6mK__sgw%2BL2_Y6M29O_%2BX%2BAk5hoaW6Q>