[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bash-bug
Subject:    Re: bash sockets: printf \x0a does TCP fragmentation
From:       dirk+bash () testssl ! sh
Date:       2018-09-25 14:13:02
Message-ID: d2a39e8a-73d4-b0ae-073b-f3d21599cfc4 () testssl ! sh
[Download RAW message or body]



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.


[prev in list] [next in list] [prev in thread] [next in thread]