Bug#1094635: /usr/bin/autopkgtest-virt-unshare: processes not killed by close

2025-01-30 Thread Ian Jackson
Control: severity -1 wishlist Jochen Sprickerhof writes ("Re: Bug#1094635: /usr/bin/autopkgtest-virt-unshare: processes not killed by close"): > I am not sure here. How should autopkgtest-virt-unshare differentiate > between processes that it should kill and unrelated

Bug#1094635: /usr/bin/autopkgtest-virt-unshare: processes not killed by close

2025-01-30 Thread Jochen Sprickerhof
* Ian Jackson [2025-01-30 14:11]: This bug is a request for autopkgtest-virt-unshare to have the capacity to kill "escaped" processes, when the testbed is closed. I think that behaviour would makes sense, perhaps even as a default. After all, the actual chroot is deleted, so any processes which

Bug#1094635: /usr/bin/autopkgtest-virt-unshare: processes not killed by close

2025-01-30 Thread Ian Jackson
Jochen Sprickerhof writes ("Re: Bug#1094635: /usr/bin/autopkgtest-virt-unshare: processes not killed by close"): > Note that autopkgtest-virt-unshare does not open some session and the > unshare syscall only changes the user namespaces for the inside > processes. Thus running

Bug#1094635: /usr/bin/autopkgtest-virt-unshare: processes not killed by close

2025-01-30 Thread Jochen Sprickerhof
Hi Ian, * Ian Jackson [2025-01-29 12:46]: Steps to reproduce: With some kind of image tarball bookworm.tar $ autopkgtest-virt-unshare -t bookworm.tar ok open ok /tmp/autopkgtest.HYR0W4 print-execute-command Then in another terminal, using that command with the commas replac