Forum: Ruby-core at_fork callback API

C4e88907313843cf07f6d85ba8162120?d=identicon&s=25 Eregon (Benoit Daloze) (Guest)
on 2013-11-30 23:12
(Received via mailing list)
Issue #5446 has been updated by Eregon (Benoit Daloze).


tmm1 (Aman Gupta) wrote:
> Simple implementation of an after_fork{} hook:
https://github.com/tmm1/ruby/commit/711a68b6599d17...
>
> Any objection?

Sounds good and useful to me!
----------------------------------------
Feature #5446: at_fork callback API
https://bugs.ruby-lang.org/issues/5446#change-43292

Author: normalperson (Eric Wong)
Status: Assigned
Priority: Low
Assignee: kosaki (Motohiro KOSAKI)
Category:
Target version: next minor


It would be good if Ruby provides an API for registering fork()
handlers.

This allows libraries to automatically and agnostically reinitialize
resources
such as open IO objects in child processes whenever fork() is called by
a user
application.  Use of this API by library authors will reduce
false/improper
sharing of objects across processes when interacting with other
libraries/applications that may fork.

This Ruby API should function similarly to pthread_atfork() which allows
(at least) three different callbacks to be registered:

1) prepare - called before fork() in the original process
2) parent - called after fork() in the original process
3) child - called after fork() in the child process

It should be possible to register multiple callbacks for each action
(like at_exit and pthread_atfork(3)).

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

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

... And any other APIs I've forgotten about

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

Ruby already has the internal support for most of this this to manage
mutexes,
Thread structures, and RNG seed.  Currently, no external API is exposed.
I can
prepare a patch if an API is decided upon.
This topic is locked and can not be replied to.