[Bug libc/19429] syslog unusable after fork from a multi-threaded program

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19429

--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Florian Weimer from comment #0)
> Technically, this is not a bug because syslog is not an async-signal-safe
> function, but maybe we should support this usage scenario as a
> quality-of-implementation issue.

Correct, per POSIX, to avoid errors, only AS-safe functions should be called.

I agree that QoI rules here and we could reset the lock.

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