18 Oct
2016
18 Oct
'16
3:10 p.m.
On 18/10/2016 18:52, Brendan Kearney wrote:
as for cli, i just created a script, that sets the env var, runs radiusd -X and then unsets the env var when i ctrl+c out of radiusd -X.
The unset is not needed. Each process has its own copy of the environment - it cannot possibly modify its parent's environment. The only case this is not true is if you use "source <scriptname>" or ". <scriptname>" to read the script directly into your running shell. If you include the shebang line (e.g. #!/bin/sh), make it executable, and execute it directly, then it's a separate process.