On Fri, 24.04.15 12:37, Jonathan Boulle (jonathanbou...@gmail.com) wrote:
Naive question, perhaps, but why does systemd even need to umount when
being run in a mount namespace? Can't we let the kernel tear them down when
it exits?
Well, so far our intention there was to ensure that the
Naive question, perhaps, but why does systemd even need to umount when
being run in a mount namespace? Can't we let the kernel tear them down when
it exits?
When rkt is started with --debug, the systemd logs are printed. When rkt
is started without --debug, systemd is started with
On Mon, 13.04.15 13:13, Alban Crequy (alban.cre...@gmail.com) wrote:
From: Alban Crequy al...@endocode.com
When a systemd-nspawn container terminates, systemd umounts all bind
mounts that were mounted in the container and generates a log for each
umount.
This additional log_info was
From: Alban Crequy al...@endocode.com
When a systemd-nspawn container terminates, systemd umounts all bind
mounts that were mounted in the container and generates a log for each
umount.
This additional log_info was added by
bce93b7ac7642426039863493694d8c12812e2a7 for debugging shutdown. But
