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


Groups > gnu.bash.bug > #14660 > unrolled thread

Re: bash sockets: printf \x0a does TCP fragmentation

Started byChet Ramey <chet.ramey@case.edu>
First post2018-09-25 09:46 -0400
Last post2018-09-25 09:46 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#14660 — Re: bash sockets: printf \x0a does TCP fragmentation

FromChet Ramey <chet.ramey@case.edu>
Date2018-09-25 09:46 -0400
SubjectRe: bash sockets: printf \x0a does TCP fragmentation
Message-ID<mailman.1296.1537883232.1284.bug-bash@gnu.org>
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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web