On Mon, Mar 10, 2014 at 04:00:45PM +0100, Christoph Berg wrote: > Control: tags -1 patch > > Re: Michael Stapelberg 2013-11-12 <[email protected]> > > Hi Antonio, > > > > Antonio Terceiro <[email protected]> writes: > > > You have to create such a chroot first, for example with > > > sbuild-createchroot(1). > > > > > > I am affected by a similar problem, which also only happens when the > > > system is booted with systemd (works fine under sysvinit): > > > > > > $ cat /etc/schroot/chroot.d/squeeze > > > [squeeze] > > > type=directory > > > description=Debian Squeeze > > > directory=/home/terceiro/chroots/squeeze > > > users=terceiro > > > groups=terceiro > > > root-users=terceiro > > > root-groups=root > > > $ schroot -c squeeze > > > (squeeze) terceiro@homer:~$ exit > > > logout > > > E: 10mount: umount: > > > /var/lib/schroot/mount/squeeze-78908cf6-2aca-4bf4-8209-fafe2260397f/tmp: > > > not mounted > > > E: squeeze-78908cf6-2aca-4bf4-8209-fafe2260397f: Chroot setup failed: > > > stage=setup-stop > > > > > > Then I have to manually finish the session: > > the problem is pretty bad - if you don't finish the session, but > re-enter it, you get new mounts for the left-over bindmounts, etc - an > exponential number of entries in /proc/mounts.
Thanks for the confirmation that the patch helps. I'll consider applying the patch. However, I won't be doing this without a good justification for why systemd has broken behaviour which has worked fine for over a decade. This isn't a schroot bug. This breaks any use of bind mounts for anyone doing a similar thing. Changing to use "shared" mountpoints is a massively breaking change, and I've not seen anything to justify it. How many admins are going to be screwed over by this? What exactly makes use of this changed behaviour, if anything? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
