Bug#810145: pbuiler: find a way to mount /run/shm even if some other process is accessing it

On Mon, Jan 22, 2018 at 11:26:31PM -0500, Sandro Tosi wrote: > I'm running 0.229 and i can confirm i no longer see this problem - thanks! I believe the situation improved a lot with 0.228 where we changed a bunch of how SHM is mounted (especially the defaults). But still if a process leaves

Bug#810145: pbuiler: find a way to mount /run/shm even if some other process is accessing it

> Hello, > when destroying the chroot, pbuilder umount run/shm, but if another process on > the system is accessing /run/shm then pbuilder keeps saying: > > umount: /var/cache/pbuilder/build/11273/run/shm: target is busy > (In some cases useful info about processes that > use the

Bug#810145: pbuiler: find a way to mount /run/shm even if some other process is accessing it

This is especially painful with the Jenkins Chroot plugin, which uses `pbuilder execute` to run things - a stray process from a failed CI test leads to gigs of "target is busy" messages in the build logs, which need manually killing. This doesn't seem inordinately difficult to resolve - lsof

Bug#810145: pbuiler: find a way to mount /run/shm even if some other process is accessing it

On Wed, Jan 6, 2016 at 5:45 PM, Sandro Tosi wrote: > when destroying the chroot, pbuilder umount run/shm, but if another process on > the system is accessing /run/shm then pbuilder keeps saying: > > umount: /var/cache/pbuilder/build/11273/run/shm: target is busy > (In

Bug#810145: pbuiler: find a way to mount /run/shm even if some other process is accessing it

Package: pbuilder Version: 0.220 Severity: normal Hello, when destroying the chroot, pbuilder umount run/shm, but if another process on the system is accessing /run/shm then pbuilder keeps saying: umount: /var/cache/pbuilder/build/11273/run/shm: target is busy (In some cases useful info