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

[bugzilla at busybox.net]

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

--- Comment #5 from mwadsten at digi.com ---
strace busybox lsof 2>&1 | grep getpid
is actually giving an empty response on this system. I did it without grep and
I definitely don't see any getpid calls.

I also don't see getpid if I do strace -F start-stop-daemon ... (not even from
the resolution of $$). Maybe that IS a sign that this glibc is caching the
getpid result (and not reaching a syscall). If I'm reading the features.h
header correctly, it's glibc 2.12.

Given that the glibc 2.25 release notes explicitly say "it was deemed safer to
remove the cache than to potentially return a wrong answer" in regards to
removing the PID cache, I assume that is the root cause here.

In that case, would you agree that we can characterize this as a busybox
compatibility issue with glibc < 2.25?

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