News for hackers. Stuff that matters.
Re:Why Ruby App Servers Break on MacOS High Sierra by throwme211345 on Thursday October 19, 2017 @08:29AM (#15507283)
LOL. mac osx breaks fork() to avoid state inconsistency in threaded applications. How about pthread_atfork() semantics? But ,as usual, apple heavy hands userspace and breaks things. Nothing new to see here, move on.
Re:Why Ruby App Servers Break on MacOS High Sierra by throwme211345 on Thursday October 19, 2017 @09:07AM (#15507511)
What you don't like the fact that apple sucks for breaking userspace (as usual) or that pthread_atfork() type approaches should be in every programmers toolbox?
Re:Why Ruby App Servers Break on MacOS High Sierra by oshepherd on Thursday October 19, 2017 @05:36PM (#15511748)
POSIX has deprecated pthread_atfork because it is unworkable. In particular, atfork handlers can only call AS-safe functions, which means they're useless.
Re:Why Ruby App Servers Break on MacOS High Sierra by throwme211345 on Friday October 20, 2017 @10:29AM (#15516041)
As you say except I explicitly noted '..type approaches' and '..semantics'. If a library designer does things in a way that makes you doubtful of state then don't fork. If you do fork block signals and exec. It doesn't help the race but it does help your peace of mind (i did what i could).

Apple still sucks BTW. Heavy handed nonsense. Let developers deal with the consequences of their actions.