Hi! On Mon, 2014-06-09 at 11:14:03 -0400, Daniel Kahn Gillmor wrote: > Package: dpkg > Version: 1.17.10 > Severity: normal
> dpkg appears to leave a file descriptor open in its children when > processing triggers. Ah! Nice catch. > When one of the children (or their descendents) invokes an lvm2 > command, lvm itself complains about the extra file descriptor. > > Is there a reason to leak the file descriptor to the child processes? No, this is just the code not setting close-on-exec for the file descriptor, I've fixed this locally for 1.17.11. W/o having checked the history, I think this has been leaking since the introduction of triggers. > i suppose it's possible to argue that the problem lies in one of these > other packages somehow -- i confess i don't understand the internals > of dpkg well enough to be sure. If you think this is an issue with a > different tool, please explain here and reassign this bug report so > that the proper tool gets fixed to avoid these spurious warnings. No, not really. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
