Not sure I follow: why do this indirectly by killing nspawn?
Why not send this to the container init directly?
Note that if you know the nspawn PID, you can derive the external PID
of the init process easily by reading
/proc/$PID/task/$PID/children. It will only container one PID, and
On Thu, 07.05.15 06:38, Peter Paule (systemd-de...@fedux.org) wrote:
I implemented this now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=c6c8f6e218995852350e5e35c080dec788c42c3f
Thanks a lot. Sorry, have seen your mail to late - I'm trying out a new
mua (sup) and I'm not
I implemented this now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=c6c8f6e218995852350e5e35c080dec788c42c3f
Thanks a lot. Sorry, have seen your mail to late - I'm trying out a new
mua (sup) and I'm not that familiar with it yet.
Do you think it makes sense to add something like
On Tue, 24.02.15 09:39, Peter Paule (systemd-de...@fedux.org) wrote:
Hi, any suggestions to cleanly shutdown containers?
If using defaults in a service file for stopping a container started with
nspawn it will be killed by SIGTERM/SIGKILL. This makes systemd-nspawn to
exit with
1 and the
On Wed, 25.02.15 20:35, Lennart Poettering (lenn...@poettering.net) wrote:
I'd be willing to take a patch that adds --kill-signal= that allows
changing the kill signal from SIGRTMIN+3 to anything else. With that
you could use --kill-signal=SIGTERM to get the behaviour you want...
I
