Date: Mon, 30 Dec 2013 22:47:10 GMT From: Robert <rol@robert-eckardt.de> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/185353: nc does not exit after transfer Message-ID: <201312302247.rBUMlAIx069715@oldred.freebsd.org> Resent-Message-ID: <201312302250.rBUMo22e020042@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 185353 >Category: amd64 >Synopsis: nc does not exit after transfer >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 30 22:50:01 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Robert >Release: 10.0-RC3 >Organization: >Environment: Live-CD from memstick >Description: nc is supposed to close connection after file transfer as described in man page. machineA or TerminalB $ nc -l 12345 > foo.txt machineC or TerminalD $ nc machineA 12345 < bar.txt The connection in the example above hangs until nc is interrupted on one side. Adding -d (don't read from stdin) on the listening side is ignored. Redirecting input from /dev/null (nc -l 12345 > foo.txt < /dev/null) on the listening side aborts before the whole file (200k in my case) was transfered. This happens also from 10.0-RC3 -> 9.1-R, but not the other way round. >How-To-Repeat: see description >Fix: >Release-Note: >Audit-Trail: >Unformatted:home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312302247.rBUMlAIx069715>