Actions
Bug #9588
closedwaitid(2): infop vs. info
Start date:
2018-06-08
Due date:
% Done:
100%
Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:
Description
The third parameter of the waitid(2) function in its manpage is always referenced as infop
with only one exception (at the last line):
RETURN VALUES If waitid() returns due to a change of state of one of its children and WNOHANG was not used, 0 is returned. Otherwise, −1 is returned and errno is set to indicate the error. If WNOHANG was used, 0 can be returned (indicating no error); however, no children may have changed state if info->si_pid is 0.
Updated by Marcel Telka about 4 years ago
Updated by Marcel Telka about 4 years ago
- Status changed from In Progress to Pending RTI
Updated by Electric Monk about 4 years ago
- Status changed from Pending RTI to Closed
- % Done changed from 0 to 100
git commit 52733287cd3e89957eb2a0c46360ce71b51a3070
commit 52733287cd3e89957eb2a0c46360ce71b51a3070 Author: Marcel Telka <marcel@telka.sk> Date: 2018-06-11T14:16:35.000Z 9588 waitid(2): infop vs. info Reviewed by: Yuri Pankov <yuripv@yuripv.net> Reviewed by: Toomas Soome <tsoome@me.com> Reviewed by: Igor Kozhukhov <igor@dilos.org> Reviewed by: Ken Mays <kmays2000@gmail.com> Approved by: Dan McDonald <danmcd@joyent.com>
Actions