http://bugzilla.suse.com/show_bug.cgi?id=1148809
http://bugzilla.suse.com/show_bug.cgi?id=1148809#c9
--- Comment #9 from Michael Chang
(In reply to Adam Spiers from comment #7)
With your test package grub2-editenv runs fine with exit code 0 (although the fd leakage is still there).
The fd leakage should be harmless, however I'll see if I could come up with a fix as well.
I'm afraid it's not in grub2-editenv, as the leaked descriptor could originate from yast bootloader, or any parent process invoking grub2-editenv, which in turn invokes vgs. I couldn't reproduce with running grub2-editenv solely from command line, but with this testing shell script it is reproducible.
#!/bin/sh exec 4<>/tmp/test grub2-editenv list
IMHO "leaked" is misleading, just some fds left opening at the time calling vgs/lvs, which shouldn't be an issue .. -- You are receiving this mail because: You are on the CC list for the bug.