[systemd-devel] You are invited to give your thoughts on some async-signal-safety issues.

[Alexander E. Patrakov]

31.08.2014 09:31, Steven Stewart-Gallus wrote:
> Hello,
>
> I understand that systemd uses sandboxing and multithreading.  After a
> fork, many things are messed up so it's only practical to use
> async-signal-safe functions after a fork from a threaded program.  If
> you have ideas on what sort of functionality GLibc needs to change to
> make systemd more async-signal-safe after a fork you are invited to
> give your thoughts on the GLibc mailing list in the thread at
> https://sourceware.org/ml/libc-help/2014-08/msg00039.html.

Sorry for a late reply, but I think you should ask Redis folks about 
async-signal safety issues. They use fork quite non-trivially for 
background saving of their database from memory to disk.

-- 
Alexander E. Patrakov