Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14647

Re: bash sockets: printf \x0a does TCP fragmentation

From Bob Proulx <bob@proulx.com>
Newsgroups gnu.bash.bug
Subject Re: bash sockets: printf \x0a does TCP fragmentation
Date 2018-09-23 12:33 -0600
Message-ID <mailman.1182.1537727595.1284.bug-bash@gnu.org> (permalink)
References <c6de6616-dda0-570d-de56-419e7676be8a@cbii-hh.de> <20180921231101307758654@bob.proulx.com> <714e1ba0-0052-2f2b-676d-778f2b7129c1@testssl.sh> <20180922111950901701520@bob.proulx.com> <948d4864-8808-9ce4-cc1e-2cce68256897@case.edu>

Show all headers | View raw


Chet Ramey wrote:
> Bob Proulx wrote:
> > It was also noted in another message that the external standalone
> > printf command line utility did buffer as you desired.  That seems
> > another very good solution too.  Simply use "command printf ..." to
> > force using the external version.
> 
> This won't work the way you want. The `command' builtin only inhibits
> execution of shell functions. It still executes builtins.  You want to
> either get the full pathname of a printf utility using `type -ap printf'
> and use that, or use the env or exec variants I recommended in my last
> message.

Oh drat!  Now I have had to learn *TWO* things today.  :-)

> > Anyway...  Since printf is a text oriented utility it makes sense to
> > me that I would operate in line buffered output mode.
> 
> It's that bash sets stdout and stderr to be line-buffered, not anything
> printf-specific.

I still think 'printf' feels more like a plain text utility and not
something one reaches for when working with binary data blobs.

Bob

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: bash sockets: printf \x0a does TCP fragmentation Bob Proulx <bob@proulx.com> - 2018-09-23 12:33 -0600

csiph-web