Re: bash sockets: printf \x0a does TCP fragmentation
From:
Chet Ramey
Subject:
Re: bash sockets: printf \x0a does TCP fragmentation
Date:
Sun, 23 Sep 2018 14:26:32 -0400
User-agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
On 9/22/18 4:22 PM, Bob Proulx wrote:
> Note that I *did* provide you with a way to do what you wanted to do. :-)
>
> 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.
>
> 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.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/