Thanks! TIL! That's a much cleaner way of doing it. Regarding keeping the file, if memory serves the "real" pipeline had some `tee`s in it. I recreated this mu

Thanks! TIL! That's a much cleaner way of doing it. Regarding keeping the file, if memory serves the "real" pipeline had some `tee`s in it. I recreated this much more recently to make a GitHub repo of funny code snippets (https://github.com/MaxBondABE/one-thread-crashing/ https://github.com/MaxBondABE/one-thread-crashing/). You reminded me of a different toy I made many years ago. I created FIFOs for files that you might try to read when exploiting an arbitrary file read in a web app, say /etc/www/apache.conf (if that's the right path - it's been a while since I've configured a web server!) and I'd have a program that opened them. This would block until someone opened the other end of the FIFO, at which point I'd raise an alarm (which was just a print statement).