Date: Mon, 22 Jul 2013 11:12:28 -0700 From: "Ronald F. Guilmette" <rfg@tristatelogic.com> To: freebsd-hackers@freebsd.org Subject: Re: bin/176713: [patch] nc(1) closes network socket too soon Message-ID: <99748.1374516748@server1.tristatelogic.com> In-Reply-To: <CAJ-VmokAhE%2Buy4-3QAW6mK__sgw%2BL2_Y6M29O_%2BX%2BAk5hoaW6Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <CAJ-VmokAhE+uy4-3QAW6mK__sgw+L2_Y6M29O_+X+Ak5hoaW6Q@mail.gmail.com> Adrian Chadd <adrian@freebsd.org> wrote: >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 Yes. >* nc decides to abort before seeing the rest of the data come in from >the remote socket Yes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99748.1374516748>