You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There might be some scenarios where the user might want to explicitly disable fork support (see #13998 for example). To support such cases, we should allow the environment variable to also have falsey values
The text was updated successfully, but these errors were encountered:
@sebbov GRPC_ENABLE_FORK_SUPPORT was added to support usage where fork is not followed by exec. A pthread_atfork() handler was added to cleanup exiting threads before fork and manage the FDs after fork. This change introduced the deadlock bug which users can run into when doing fork/exec. As a quick workaround, GRPC_ENABLE_FORK_SUPPORT when set to false doesn't invoke this new logic. At this point this is tribal knowledge. A fix will be coming soon.
lockbot
locked as resolved and limited conversation to collaborators
Sep 30, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently we could only set the environment variable
GRPC_ENABLE_FORK_SUPPORT
to truthy values (see https://github.com/grpc/grpc/blob/v1.8.4/src/core/lib/support/fork.cc#L43)There might be some scenarios where the user might want to explicitly disable fork support (see #13998 for example). To support such cases, we should allow the environment variable to also have falsey values
The text was updated successfully, but these errors were encountered: