This repository has been archived by the owner on May 6, 2020. It is now read-only.
Don't need to reap the zombie child anymore since libcontainer has been fixed #88
Assignees
Comments
sboeuf
pushed a commit
that referenced
this issue
Aug 22, 2017
The latest version of libcontainer introduces a fix to reap the defunct child process so that we don't have to do that from our agent anymore. This is pretty logical since the lib is starting the process on our behalf, therefore they know they are leaving a zombie process behind. Fixes #88 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
|
\o/ |
sboeuf
pushed a commit
that referenced
this issue
Aug 22, 2017
The latest version of libcontainer introduces a fix to reap the defunct child process so that we don't have to do that from our agent anymore. This is pretty logical since the lib is starting the process on our behalf, therefore they know they are leaving a zombie process behind us. Fixes #88 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We had to reap the child zombie process because we were leaving some defunct child processes behind after we have started some processes. The reason was that libcontainer was not doing this for us.
It now has been fixed in libcontainer and we don't need our fix anymore.
The text was updated successfully, but these errors were encountered: