bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bash sockets: printf \x0a does TCP fragmentation


From: Bob Proulx
Subject: Re: bash sockets: printf \x0a does TCP fragmentation
Date: Sun, 23 Sep 2018 12:33:07 -0600
User-agent: Mutt/1.10.1 (2018-07-13)

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]