You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2017/11/15 08:58:00 UTC
[jira] [Created] (MESOS-8229) Make it possible to reliably inject
environment variables into forked processes
Benjamin Bannier created MESOS-8229:
---------------------------------------
Summary: Make it possible to reliably inject environment variables into forked processes
Key: MESOS-8229
URL: https://issues.apache.org/jira/browse/MESOS-8229
Project: Mesos
Issue Type: Improvement
Components: agent, containerization, master
Reporter: Benjamin Bannier
We should consider supporting reliable injection of environment variables into forked processes, e.g., to customize dynamic library loading with {{LD_PRELOAD}} or the influence the behavior of the used runtime (e.g., glibc options). Customary, environment variables are used for this, but we tend to in many cases strip away all but a hardcoded set of flags (e.g., when starting executors). The possible set of these flags seems to be open.
I came across this when trying to run our test suites with a build with clang address sanitization enabled (passing {{-fsanitize=address}} in the compiler flags). This links in a C runtime which aborts processes if memory leaks are detected. These aborts can be disabled by passing runtime options in an environment variable {{ASAN_OPTIONS}}, but unfortunately, it is not effective in all forked processes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)