3 ms·

> Other than that, it can also be handy in k8s with a VPA. You get more/less memory and then update the env to reflect that. Your service picks up the env chang

• withinboredom 3y ago
  You can spawn as many processes as you want in a container, did you not know that? But you only need access to the /proc/pid directory to change another processes env.
  • eqvinox 3y ago
    > But you only need access to the /proc/pid directory to change another processes env. /proc/$pid/environ is not writable (and as a matter of fact, due to how the environment works, it cannot be writable.)
    • LegionMammal978 3y ago
      But /proc/pid/mem is, if you like living dangerously! You'd just have to parse the dynamic-linker metadata to find where libc's environ is hiding. (Though statically-linked programs would be tougher.)
  • SAI_Peregrinus 3y ago
    Spawning a new process doesn't require changing the parent's environment.
• pjc50 3y ago
  > You… can't change the env from outside the process… Not with that attitude you can't. (OK, without the joke: you can do this with an interactive debugger. But I think OP just meant "change it in the container and then restart the child process")