On Sun, Sep 14, 2014 at 3:38 PM, Roger Leigh <rle...@codelibre.net> wrote: > On Sat, Sep 13, 2014 at 02:01:06PM -0700, Ben Longbons wrote: >> >> I don't use schroot very often, and I recently noticed that when I use >> it, the inner system is missing all its mounts. In particular, there is >> nothing mounted on /proc or /dev/pts, but there is a private /tmp/ that >> is persistent even after schroot exits. >> >> Upgrading to the version in experimental does NOT help. >> >> I do use systemd, and I don't think I've successfully used schroot since >> I switched. > > What do you mean by "inner system" here? The Ubuntu installation inside the chroot.
> I would suggest running with the "-v" options to make schroot display all > the mount/umount operations as well as all the other setup and cleanup > work. Do you see anything missing or failing? All the setup/cleanup is > done via the setup scripts in /etc/schroot/setup.d, so it should be > possible to add additional diagnostics to the scripts to see what's > going wrong. I added 'set -x' to all of the scripts and there is no additional output. This seems very bizarre. > You can also run with "--debug=notice", which will give even more details > about the schroot internals, but I'm not sure in this case it will reveal > much of interest; I'd recommend "-v" though. -v didn't show anything, so attachment 'schroot-debug' is the output of running (as root) schroot --debug=notice -c precise mount, modified carefully to remove only the other chroots and the host environment variables. Incidentally I purged schroot's config and the reinstalled the jessie/sid version before running this (keeping only my choots and custom profile).
schroot-debug
Description: Binary data
