Attaching file descriptors to processes with CLONE_FD

Posted Apr 3, 2015 7:16 UTC (Fri) by iq-0 (subscriber, #36655)
In reply to: Attaching file descriptors to processes with CLONE_FD by josh
Parent article: Attaching file descriptors to processes with CLONE_FD

SIGCHLD is a relic and it's interface reflects what was available at the time.

Most programs only care about exit status. But for anybody who is interested in resource usage, I think nobody want to know only the cpu timings. Most programs make do with it, but that is more a case of what they got, not what they want.

We are talking about 144 bytes vs 32 bytes per exited process that has not been reaped. The pointers inside the kernel for basic administration are probably more expensive to keep around.

Attaching file descriptors to processes with CLONE_FD

Posted Apr 3, 2015 7:35 UTC (Fri) by iq-0 (subscriber, #36655) [Link]

Not to say that getrusage may not be the best alternative perse, pherhaps BSD process accounting of similar structure might be a better match.

Attaching file descriptors to processes with CLONE_FD

Posted Apr 3, 2015 8:20 UTC (Fri) by josh (subscriber, #17465) [Link] (1 responses)

That's making me tempted to just drop the CPU usage numbers and only keep the status and code, with getrusage available for anything else.

Attaching file descriptors to processes with CLONE_FD

Posted Apr 3, 2015 8:49 UTC (Fri) by iq-0 (subscriber, #36655) [Link]

Sure, accounting information could easily be envisioned as a future improvement when the need arises (and when the need arises it will be much clearer what kind of information is desired).