`time(1)` and children - GNU/Linux

Users browsing this thread: 1 Guest(s)
I love those deep dives driven by questioning about how things actually works internally.

time(1) is misleading because its goal isn't to output something for humans, its goal is to give resource usage, so if a process is composed of multiple threads or sub-processes the time is going to be cummulative. Though, I had no clue it was actually implemented through wait(3) (or other implementations of wait), but this makes total sense for accounting and traceability.

I'll link your article in this section of mine, helping those pesky search engines know where to find the good stuff.

Messages In This Thread
`time(1)` and children - by movq - 29-08-2020, 05:43 AM
RE: `time(1)` and children - by venam - 29-08-2020, 06:21 AM
RE: `time(1)` and children - by movq - 31-08-2020, 10:04 AM