> An environment variable's value, for a running process, is just what it is: an initial value from outside. Then calling setenv() from anywhere except in the

> An environment variable's value, for a running process, is just what it is: an initial value from outside. Then calling setenv() from anywhere except in the time between a fork() and exec() call should be banned, but it's not. Honestly, calling abort() if setenv is called in the presence of threads would seem like a better status-quo than what we have today.