Bug#391319: [Buildd-tools-devel] Bug#391319: schroot: leftover processes cause umount to fail

2007-05-28 Thread Roger Leigh
tags 391319 + fixed-upstream pending thanks Kees Cook [EMAIL PROTECTED] writes: On Wed, May 23, 2007 at 08:38:15PM +0100, Roger Leigh wrote: This is already true. If no proc items are found to kill, the function immediately exits. Great. I think the while loop needs some optimisation,

Bug#391319: [Buildd-tools-devel] Bug#391319: schroot: leftover processes cause umount to fail

2007-05-28 Thread Kees Cook
Hi Roger, On Mon, May 28, 2007 at 01:17:30PM +0100, Roger Leigh wrote: This is fantastic. I have separated it from 10mount, as 15killprocs (it will always get run before 10mount on shutdown). This is because you might want to run it even if there are no filesystems to unmount. Ah, yes.

Bug#391319: [Buildd-tools-devel] Bug#391319: schroot: leftover processes cause umount to fail

2006-10-07 Thread Roger Leigh
Kees Cook [EMAIL PROTECTED] writes: While using schroot on LVM snapshots with sbuild, I have sometimes run into situations where build deps start up services (like cron, dbus, etc). Once the build is finished, schroot attempts to umount and destroy the LVM snapshot, but since there are still

Bug#391319: [Buildd-tools-devel] Bug#391319: schroot: leftover processes cause umount to fail

2006-10-07 Thread Kees Cook
On Sat, Oct 07, 2006 at 10:54:10AM +0100, Roger Leigh wrote: One concern I have is what will happen to bind mounted filesystems, or filesystems mounted multiple times? If there are open files, we don't want to kill anything /outside/ the chroot, which may also be using the filesystem. Ah,