Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14663 > unrolled thread
| Started by | dirk+bash@testssl.sh |
|---|---|
| First post | 2018-09-25 16:13 +0200 |
| Last post | 2018-09-25 16:13 +0200 |
| 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.
Re: bash sockets: printf \x0a does TCP fragmentation dirk+bash@testssl.sh - 2018-09-25 16:13 +0200
| From | dirk+bash@testssl.sh |
|---|---|
| Date | 2018-09-25 16:13 +0200 |
| Subject | Re: bash sockets: printf \x0a does TCP fragmentation |
| Message-ID | <mailman.1299.1537884797.1284.bug-bash@gnu.org> |
On 9/25/18 3:46 PM, Chet Ramey wrote: > 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. yeah, you're right.
Back to top | Article view | gnu.bash.bug
csiph-web