Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Where did you get this crazy code from? Assuming you are using bash, <( somecomand ) redirects the output to a file descriptor, so it can be used in place of a file. sleep does not produce any output. Commented Aug 17 at 14:59
  • @GyroGearloose Those commands are my own. They are just to test my understanding of what is happening. I know that sleep doesn't produce any output, I only used it to have some time to have a look at the file descriptors associated to the different processes. I then realized I could use read instead in order to "block" the execution of the command in the background while looking into the /proc/<PID> directories. Commented Aug 17 at 15:11
  • @GyroGearloose, sleep still inherits an stdout file descriptor from its parent, and the fact that it doesn't print anything isn't really relevant to how the plumbing is set up. (Consider that the program inside could be something like find, which may or may not print something.) Commented Aug 17 at 15:16