Yes. The "tree" starting at dpkg was linear, with one child for each process, except for who which was a leaf.
I just had a look at the code. /usr/lib/python2.5/site-packages/landscape/lib/sysstats.py uses twisted.internet.utils.getProcessOutputAndValue to call "who -q". Therefore the actual cause of this bug might also lie in python-twisted-core, which might for some reason have failed to reap this dead child. Should this bug here therefore be marked as affecting twisted as well as landscape-client?
I cannot reproduce the issue by calling landscape-sysinfo manually. If I hadn't been in such a hurry, I might have thought of stracing landscape-sysinfo, but it's too late for that now.
Yes. The "tree" starting at dpkg was linear, with one child for each process, except for who which was a leaf.
I just had a look at the code. /usr/lib/ python2. 5/site- packages/ landscape/ lib/sysstats. py uses twisted. internet. utils.getProces sOutputAndValue to call "who -q". Therefore the actual cause of this bug might also lie in python- twisted- core, which might for some reason have failed to reap this dead child. Should this bug here therefore be marked as affecting twisted as well as landscape-client?
I cannot reproduce the issue by calling landscape-sysinfo manually. If I hadn't been in such a hurry, I might have thought of stracing landscape-sysinfo, but it's too late for that now.