hi, bastian, On Wed, Aug 29, 2007 at 02:44:25PM +0200, Bastian Kleineidam wrote: > Am Sonntag, 26. August 2007 19:23:19 schrieb ingo: > > What seems to happen in the former case is that 'mount' creates a first > > loop device and only after that passes this loop device to mount.crypt > > which creates an additional loop device by itself. > Yes, that's what happens. Please try the attached patch and tell if it helps.
yep, with the original pam_mount.conf setup, only one loop device gets created on login and everything is cleaned up on umount. > > ah, and i tried 'umount -t crypt' but that was even worse, > > it did just a normal umount without considering all the special stuff. > I noted that too and consider it a bug of umount. I will file a separate bug > report about that. i suppose this should not event depend on a -t option to umount. thanks, ingo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
