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


Groups > gnu.bash.bug > #14660

Re: bash sockets: printf \x0a does TCP fragmentation

From Chet Ramey <chet.ramey@case.edu>
Newsgroups gnu.bash.bug
Subject Re: bash sockets: printf \x0a does TCP fragmentation
Date 2018-09-25 09:46 -0400
Message-ID <mailman.1296.1537883232.1284.bug-bash@gnu.org> (permalink)
References (1 earlier) <20180921231101307758654@bob.proulx.com> <714e1ba0-0052-2f2b-676d-778f2b7129c1@testssl.sh> <20180922111950901701520@bob.proulx.com> <948d4864-8808-9ce4-cc1e-2cce68256897@case.edu> <bd1b9a9c-a515-3900-a7b3-17548694d4df@testssl.sh>

Show all headers | View raw


On 9/25/18 9:04 AM, dirk+bash@testssl.sh wrote:

> FYI: I ended up checking with type before whether an external printf
> exists and set a variable for this and then just call this variable.
> 
> env or exec: never thought about it (thanks!) but as both are external
> commands, that would mean upon every call one additional external program.
> (yes, I know that there is such thing as a fs buffer). Subshells also costs
> resources. As this is a core function I am happy for every homeopathic dose
> of time I safe here :-)

`exec' is a shell builtin. It will `cost' in terms of a fork, but you're
going to fork and exec a different program anyway -- /usr/bin/printf --
so it's basically a wash. In either case, there's one fork and one
execve.

-- 
``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/

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


Thread

Re: bash sockets: printf \x0a does TCP fragmentation Chet Ramey <chet.ramey@case.edu> - 2018-09-25 09:46 -0400

csiph-web