Date: Mon, 2 Jan 2023 03:18:37 +0200
On Mon, 2 Jan 2023 at 02:36, Corentin Jabot via Lib-Ext
<lib-ext_at_[hidden]> wrote:
> Moreover, the ability to modify the view over the environment makes the thing hard to use, if not pointless.
> If someone overrides the value of an environment variable, there is no (easy/portable/reliable) way to get to the original value (which was put there by the parent process).
> This is an issue for example with libraries overwriting "LC_XXX", thereby making them unusable to determine how to communicate with the parent process.
Seems like a rather unfortunate situation when I can't write that
parent process program in C++ when the most suitable way to launch
the child is to set up the current environment and fork().
<lib-ext_at_[hidden]> wrote:
> Moreover, the ability to modify the view over the environment makes the thing hard to use, if not pointless.
> If someone overrides the value of an environment variable, there is no (easy/portable/reliable) way to get to the original value (which was put there by the parent process).
> This is an issue for example with libraries overwriting "LC_XXX", thereby making them unusable to determine how to communicate with the parent process.
Seems like a rather unfortunate situation when I can't write that
parent process program in C++ when the most suitable way to launch
the child is to set up the current environment and fork().
Received on 2023-01-02 01:18:50