This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/19429] syslog unusable after fork from a multi-threaded program
- From: "derek at idirect dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 18 Feb 2016 00:27:14 +0000
- Subject: [Bug libc/19429] syslog unusable after fork from a multi-threaded program
- Auto-submitted: auto-generated
- References: <bug-19429-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19429
--- Comment #2 from Derek Snider <derek at idirect dot com> ---
Just to add to this, through debugging this issue I've noticed that it seems
that the fork() call can be interrupted by a signal handler before it
completes. I would expect that an operation such as fork() should ignore
signals, no? I didn't think that I would have to block signals myself before
calling fork() and restore them afterwards.
--
You are receiving this mail because:
You are on the CC list for the bug.