guyarb

> Programs can and will exit before the userspace daemon is able to read from /proc that's depend on the use case, and we are mainly tracking server which are not terminated during our runtime. of course if we are tracking "not servers" (like curl) it can happen, and for that you can find other fallbacks. regardless, we cannot assume we will be existing before all other server and client have started running, so we are trying to do "best effort", that's why counting on hooking the `exec` syscalls is not robust either.

I feel the same, but I wanted to find the "common" description for containers, and I kept seeing the same description, finally I used that term, and quoted one of the sources I found for it.

first of all, thanks for the ps aux mistake, I fixed it (the correct entry point is `tiny -- /run.sh`)

regarding the question, it depends on the use case, I'm mainly tracking servers which are not terminated therefore it works good enough for me but of course if I'm capturing clients (for example curl) it might be problematic for such use-cases we have additional fallbacks, adding the kernel comm task along with the PID, or to hook `execv` and `fork` to have more time before the process is being terminated