Bug #2728
closed
Sudo doesn't reap it's children
Added by zcrownover about 10 years ago.
Updated about 10 years ago.
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
- Category changed from Kernel to Vendor software
Sudo 1.8.10 is actually fine, changing category to Vendor software
- Target version changed from 3.9.x to 4.0
Changing target version to 4.0
sudo-1.8.11.p1 is working fine on FreeBSD -current, this may still be a DragonFly bug.
I forgot to mention it, but for clarity sake, the file I attached earlier is a ktrace file.
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?
- % Done changed from 0 to 100
- Status changed from New to Resolved
The patched sudo is now in dports and will be in the next set of 4.0 packages.
- Status changed from Resolved to Closed
Also available in: Atom
PDF