to, 2006-09-14 kello 21:23 +1000, Aníbal Monsalve Salazar kirjoitti: > Since I upgraded piuparts from 0.17-1, I'm getting the following > error message: Processes are running inside chroot. > > 2m32.3s DEBUG: Command failed (status=256), but ignoring error: 'lsof +D > /tmp/tmphOpFXk' > 2m32.3s ERROR: Processes are running inside chroot: > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > update-me 29928 root cwd DIR 3,1 4096 709635 /tmp/tmphOpFXk > update-me 29928 root rtd DIR 3,1 4096 709635 /tmp/tmphOpFXk > update-me 29928 root txt REG 3,1 129272 761519 > /tmp/tmphOpFXk/usr/bin/update-menus
The cause of this problem is that update-menus forks itself into the background in some cases (if dpkg status area is locked, I think), and waits there until it can continue. Depending on timing, it may or may not be able to finish by the time piuparts runs lsof. I'm not sure what should be done about this. As I understand it, update-menus is correct in forking, and piuparts is correct in diagnosing it as a still-running process. It would be possible, though awkward, to add ignore features for processes in the lsof output. I'd rather not do that; instead, it might be better to special case update-menus and wait for its pid file to go away before running lsof. I'll have to think about this. As it happens, nothing should have changed since 0.17-1 related to this. It's just a random timing issue, dependent on (for example) speed of the machine and it's I/O load. -- "Quack, damn you!" -- Jamie Hyneman
