Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point

2020-12-16 Thread Craig Small (enc)
On Fri, 29 Apr 2016 at 06:31, Franco Martelli wrote: > $ fuser -M > /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c > Specified filename > /var/lib/schroot/mount/kubuntu-e1c05063-2aca-491c-b5e4-4a4e1c41c65c is > not a mountpoint. > > fuser now tell me that it wasn't a mount

Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point

2016-04-28 Thread Franco Martelli
For sake of clarity this is a schroot command issue related bug report, all works fine with chroot ordinary command. As you suggest I try the -M switch, once started schroot's session: $ kubuntu then open a new console and run these commands: ~# killall cupsd ~# service cups start then come back

Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point

2016-04-24 Thread Craig Small
The problem is that fuser works off device numbers (it has to otherwise symlinks would confuse it) and there is nothing much that makes the chroots unique. A chroot is basically saying "start your tree here". My chroots for example sit under /var/chroot Now, outside the chroot I can work out what

Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point

2016-03-08 Thread Franco Martelli
On 08/03/2016 at 10:52, Craig Small wrote: > It actually finds the process you are looking for, however it also finds > a lot of other processes. Yes, this is true, sorry my mistake. > > ~# fuser -m > /var/lib/schroot/mount/kubuntu-a3ca1d7f-7fce-4673-b84a-6c4835bd7316 > > Find something

Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point

2016-03-08 Thread Craig Small
On Sun, Mar 6, 2016 at 8:33 AM Franco Martelli wrote: > The "fuser" command does not print nothing about PID of processes that > keep busy a schroot's generated mount-point. Error messages when I > logout a schroot session: > > It actually finds the process you are looking

Bug#816861: fuser does not show the PID that keeps busy a schroot mount-point

2016-03-05 Thread Franco Martelli
Package: psmisc Version: 22.21-2 The "fuser" command does not print nothing about PID of processes that keep busy a schroot's generated mount-point. Error messages when I logout a schroot session: ~$ logout E: 10mount: rmdir: failed to remove