> 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 cleanly is: * started from a systemd unit rather than from the sysv init script * they set PrivateTmp=yes in the unit PrivateTmp=yes causes a new mount namespace to be created. (For those wondering how to get rid of schroot sessions that schroot doesn't seem to be able to clean up, shutdown the daemons involved, schroot -e --all- sessions, restart the daemons) cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ [email protected] Debian Developer http://www.debian.org/ [email protected] GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
