Date: Wed, 1 Jan 2014 15:20:01 GMT From: "Robert Eckardt" <rol@robert-eckardt.de> To: freebsd-amd64@FreeBSD.org Subject: Re: amd64/185353: nc does not exit after transfer Message-ID: <201401011520.s01FK1xS039931@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR amd64/185353; it has been noted by GNATS. From: "Robert Eckardt" <rol@robert-eckardt.de> To: Peter Wemm <peter@wemm.org> Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/185353: nc does not exit after transfer Date: Wed, 1 Jan 2014 16:10:24 +0100 On Mon, 30 Dec 2013 16:40:42 -0800, Peter Wemm wrote > -N shutdown(2) the network socket after EOF on the input. > Some servers require this to finish their work. > > Try: "nc -N machineA 12345 < bar.txt" from your example Hi, you're right. It works. Then it should be documented in the example in the man page as nc now belongs to "some servers" that require this to finish their work. Regards, Robert > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; > KI6FJV Yes, I know, gmail sucks now. If you see this then I forgot. Habits > are hard to break.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201401011520.s01FK1xS039931>