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*

2
  • Hmm... since your "foo" program is not just a simple single-process, single-threaded process, you would be better served by telling strace to follow and attach to forks. '-ff' is your friend! :) You'll also want to, then, use "-o /dev/shm/strace-foo" to corrall all those strafe process output files into one location. Just a suggestion. Commented Jan 31, 2018 at 18:38
  • @JesseAdelman I think journalctl runs one process only. I have a feeling journalctl uses one extra thread for whatever reason - iirc there was one clone() call. I think this means you are technically correct, but it is also technically irrelevant to the question. time looks at the process as a whole, and has shown that the process as a whole is rather sleepy (blocking on something). strace did not show enough sleeps. It doesn't matter if a second thread is sleeping, the main thread must also be very sleepy to explain the time result. Commented Jan 31, 2018 at 20:41