Greg Wooledge (HE12025-12-23): > You might be surprised by how many temp files are used by various > programs on a regular basis, then. Historically, bash always used > a temp file for every here document (<<) or here string (<<<). It's > only in the most recent versions that bash started using pipes for > shorter here docs, and falling back to temp files for larger ones.[1]
I am indeed surprised, thanks for the history tidbit. > I lack the knowledge to test it personally by any means other than > watching the disk activity light, which is much harder to do now, > compared to the old days. I would suggest: generate a random sequence of octets, *do not write it to disk*, scan the whole block device to check it is not there. Then write it into a file, remove the file immediately and scan again. Which I did, and I am humbled to say that you were right. I find that quite surprising and would need to look at how it is implemented. Regards, -- Nicolas George
