From: Eric Wong <normalperson@...>
Date: 2018-07-19T17:37:30+00:00
Subject: [ruby-core:88008] Re: [Ruby trunk Feature#5446] at_fork callback API

ashe@kivikakk.ee wrote:
> Are we still interested in pursuing something like this? I'd
> be happy to push it forward.

I'm not sure it's necessary, anymore.  Most programs and libs
already have workarounds at this point.  pthread_atfork can also
be the source of surprising behaviors (thread/async-signal
safety), so Austin group proposed _Fork function:
http://austingroupbugs.net/view.php?id=62

> https://bugs.ruby-lang.org/issues/5446#change-73019

> These callbacks should be called whenever fork() is used:

> - IO.popen
> - ``
> - Kernel#system

Furthermore, many platforms have vfork (it's possible to support
vfork without MMU) and we favor using that for process spawning,
so the following is unneccessary:

> I also want to consider handlers that only need to be called for plain
> fork() use (without immediate exec() afterwards, like with `` and system()).

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>