[Bug 13856] Wrong PID written by start-stop-daemon -S -b -m -p

bugzilla at busybox.net bugzilla at busybox.net
Wed Jun 16 09:54:13 UTC 2021


https://bugs.busybox.net/show_bug.cgi?id=13856

--- Comment #1 from Denys Vlasenko <vda.linux at googlemail.com> ---
(In reply to mwadsten from comment #0)
> In any case, it is technically incorrect to use vfork the way
> that debianutils/start-stop-daemon.c does, because there is no
> defined guarantee that the result of getpid() in the grandchild process is correct.

Can you expand on this? Where does it say that getpid() after vfork() is not
guaranteed to return correct value?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the busybox-cvs mailing list