From owner-freebsd-stable@FreeBSD.ORG Tue Feb 11 00:23:02 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0FE9C977 for ; Tue, 11 Feb 2014 00:23:02 +0000 (UTC) Received: from teaspoon.mischlersflorist.com (rrcs-72-45-221-198.nys.biz.rr.com [72.45.221.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A81241AB3 for ; Tue, 11 Feb 2014 00:23:01 +0000 (UTC) Received: from [192.168.254.253] ([192.168.254.253]) by teaspoon.mischlersflorist.com (8.14.7/8.14.5) with ESMTP id s1B0GCWn011638 for ; Mon, 10 Feb 2014 19:16:12 -0500 (EST) (envelope-from dave@mischler.com) Subject: Is "nc" broken in 10.0? From: Dave Mischler To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" Date: Mon, 10 Feb 2014 19:16:11 -0500 Message-ID: <1392077771.9826.4.camel@barrel.mischler.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: dave@mischler.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 00:23:02 -0000 the 'nc' program doesn't seem to close the network connection anymore when it reaches EOF. This worked fine in 9.x. Can somebody else confirm this broken behavior? Example: On one session, listen for an incoming connection: % nc -l 5101 On another session, open an outgoing connection, then close the input: % nc 127.0.0.1 5101 ^D The session will not close. It doesn't seem to matter if the input is a terminal, file, pipe, or whatever else you can think of.