[systemd-devel] Significant performance loss caused by commit a65f06b: journal: return -ECHILD after a fork

[Reindl Harald]

Am 12.07.2017 um 10:23 schrieb Lennart Poettering:
> On Wed, 12.07.17 09:51, Florian Weimer (fw at deneb.enyo.de) wrote:
>> Fork detection using getpid is not reliable.  It gives false negatives
>> in the case of double-forks, where the process can be different but
>> the PID is the same due to reuse.  Considering that this use case is
>> broken, I don't think it's worthwhile to jump through hoops to support
>> code which is fundamentally broken anyway.
> 
> Uh, that's a bit non-chalant, no? Yes, the UNIX PID concept is awfully
> designed, but if you argue on that level, you#d have to remove kill(),
> and half of the other syscalls that take a PID from glibc too...

don't get me wrong: this is exactly how you argue to all others over 
years "fundamentally broken anyway, fix it"