Closed mortonne closed 7 years ago
This issue doesn't come up too often, but I will update the environment propagation script to quote variable values with spaces in them.
I have been looking at the previous environment propagation script (from version 1.4), and it simply doesn't propagate variables with spaces in them.
Also, I do not see a way to escape the spaces so that env will not interpret them as separate arguments. Surrounding in quotations and using backslashes do not work.
Going forward, pass_env will simply ignore all variables which contain spaces.
I have fixed the pass_env
script so that variables with spaces are not propagated.
On TACC's Lonestar 5, with launcher 3.0.1, I see a minor issue where paramrun crashes during the environment inheritance process if there is any variable in the environment whose value has spaces. For example:
jobfile just contains a series of echo "Hello, World!" statements. I didn't see this issue on Lonestar 4 using launcher 1.4. A simple workaround, of course, is just to not have any environment variables with spaces in them. I wanted to log this anyway, partly just so other users will know about this.