Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Aug 2016 17:26:17 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 211579] Remove socket support in cat(1)
Message-ID:  <bug-211579-8-j3G3oYeMln@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211579-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-211579-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211579

John Baldwin <jhb@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhb@FreeBSD.org

--- Comment #5 from John Baldwin <jhb@FreeBSD.org> ---
While 'nc' would seem to the obvious replacement, I haven't yet found a way=
 to
get equivalent functionality.  I use 'nc -kU -l /tmp/sock' to create a sock=
et.=20
I can then type into that terminal to store data in netcat's "buffer".  'cat
/tmp/sock' drains whatever data is pending and exits.  'nc -dNU /tmp/sock'
comes close to this except that it will still block if there is no pending =
data
instead of exiting with null output.  Also, given that existing scripts, et=
c.
might depend on this feature of cat (given it's been present for so long), =
it
seems best to just leave well enough alone in this case.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211579-8-j3G3oYeMln>