Re: [systemd-devel] [PATCH v3 2/2] nspawn: make nspawn robust to container failure

2014-06-02 Thread Djalal Harouni
On Sun, May 25, 2014 at 05:28:13AM +0200, Lennart Poettering wrote: > On Sat, 24.05.14 14:58, Djalal Harouni (tix...@opendz.org) wrote: > > Applied both. Thanks! Ok, thanks! > However, I am not too convinced about the clone() thing in > shared/eventfd-util.[ch]. That sounds too specific to be sha

Re: [systemd-devel] [PATCH v3 2/2] nspawn: make nspawn robust to container failure

2014-05-24 Thread Lennart Poettering
On Sat, 24.05.14 14:58, Djalal Harouni (tix...@opendz.org) wrote: Applied both. Thanks! However, I am not too convinced about the clone() thing in shared/eventfd-util.[ch]. That sounds too specific to be shared betwen more than one tool. I have the suspicion that we really should move that code b

[systemd-devel] [PATCH v3 2/2] nspawn: make nspawn robust to container failure

2014-05-24 Thread Djalal Harouni
nspawn and the container child use eventfd to wait and notify each other that they are ready so the container setup can be completed. However in its current form the wait/notify event ignore errors that may especially affect the child (container). On errors the child will jump to the "child_fail"