News for hackers. Stuff that matters.
Re:Why Ruby App Servers Break on MacOS High Sierra by wruza on Thursday October 19, 2017 @05:36AM (#15506593)
EINTR? I suspect some calls are defined to never return it, but it may be just de facto, not strict rule.

Edit: simply signalling all threads with SIGFORK, waiting for a handler to return and freezing a thread at SA_RESTART point feels right way to do it. Why did POSIX decide to fork() only one thread by default at all?

Re:Why Ruby App Servers Break on MacOS High Sierra by crest on Thursday October 19, 2017 @06:57AM (#15506874)
Because the alternatives are worse.