Bug#749897: [buildd-tools-devel] Bug#749897: schroot: Can't end session after schroot automatically restored it during boot under systemd

So, it turns out the problem is not systemd uses a different namespace as I originally thought, but if daemons starting after a schroot session starts uses its own mount namespace, it prevents schroot -e from working. Indeed, a common feature of the services that cause schroot to fail to exit

Bug#749897: [buildd-tools-devel] Bug#749897: schroot: Can't end session after schroot automatically restored it during boot under systemd

tags 749897 + moreinfo On Fri, May 30, 2014 at 10:07:24PM +0900, Mike Hommey wrote: So, I had three schroot sessions active and at some point, there was a reboot involved. I don't remember if it was a hard reboot or a soft reboot, because it was actually a while ago, but it doesn't matter

Bug#749897: [buildd-tools-devel] Bug#749897: schroot: Can't end session after schroot automatically restored it during boot under systemd

retitle 749897 Can't end session if daemon starting after a schroot session is created uses a private mount namespace. tag 749897 - moreinfo thanks On Tue, Jul 15, 2014 at 09:48:58PM +0100, Roger Leigh wrote: tags 749897 + moreinfo On Fri, May 30, 2014 at 10:07:24PM +0900, Mike Hommey wrote: