Date: Mon, 22 Jul 2013 19:28:23 -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-Vmonk-8v9ej0w4qycNNBkieOeE9dL3BTVp6VqipxKH2jSUA@mail.gmail.com> In-Reply-To: <99748.1374516748@server1.tristatelogic.com> References: <CAJ-VmokAhE%2Buy4-3QAW6mK__sgw%2BL2_Y6M29O_%2BX%2BAk5hoaW6Q@mail.gmail.com> <99748.1374516748@server1.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Right, and your patch just stops the shutdown(), right? Rather than teaching nc to correctly check BOTH socket states before deciding to close things. I'd personally rather see nc taught to check to see whether it can possibly make ANY more progress before deciding to shut things down. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmonk-8v9ej0w4qycNNBkieOeE9dL3BTVp6VqipxKH2jSUA>