Bug #2728
closed
Sudo doesn't reap it's children
100%
Description
Sudo fails to reap it's child processes, leaving zombies and never returning to the original prompt. Sudo then fails to listen to term signals, requiring kill signals to take them down. This affects the latest version of sudo in the packages and tested on the 4.0 RC. To be clear, sudo commands will be invoked successfully, but the prompt will not be returned. Although I've marked this as 3.9, it's actually for 4.0, the versions here need to be updated.
pkg query %n-%v sudo
sudo-1.8.11.p1
Files
Updated by ftigeot over 9 years ago
- Category changed from Kernel to Vendor software
Sudo 1.8.10 is actually fine, changing category to Vendor software
Updated by ftigeot over 9 years ago
- Target version changed from 3.9.x to 4.0
Changing target version to 4.0
Updated by ftigeot over 9 years ago
Bug reported upstream at http://www.sudo.ws/bugs/show_bug.cgi?id=676
Updated by ftigeot over 9 years ago
sudo-1.8.11.p1 is working fine on FreeBSD -current, this may still be a DragonFly bug.
Updated by zcrownover over 9 years ago
I forgot to mention it, but for clarity sake, the file I attached earlier is a ktrace file.
Updated by dragonflybsd1 over 9 years ago
joris mentions the patch provided in that ticket worked.
What happens with that patch? pushed to freebsd ports? Are they not affected by the issue -- truly? why not?
Updated by ftigeot over 9 years ago
- % Done changed from 0 to 100
The fixes for this bug have been pushed to DeltaPorts.
https://github.com/DragonFlyBSD/DeltaPorts/commit/81a01d411a95b21341361e0d30d4a571edf5f610
Hopefully this is temporary and a new sudo version will include them in the future.
Updated by ftigeot over 9 years ago
- Status changed from New to Resolved
The patched sudo is now in dports and will be in the next set of 4.0 packages.
Updated by