t; I really don't understand how this new namespace thing is expected to
> > work.
Mount namespaces are now quite an old feature; they were introduced in
Linux 2.4.19. However, systemd changes the default propagation mode
for mount namespaces to "shared", i.e. new mount
I recently noticed that schroot could no longer tidy up chroots it had
finished with. Much investigation with the help of debian Bug #749897
revealed that there is a problem with the combination of schroot,
systemd and demons that use the 'private mount namespace'
feature. (PrivateTmp=yes in the s
2 matches
Mail list logo
