Skip to content

Comments

Exclude GNU Screen environmental variables in pass_env#66

Open
AJVincelli wants to merge 2 commits intoTACC:masterfrom
AJVincelli:patch-1
Open

Exclude GNU Screen environmental variables in pass_env#66
AJVincelli wants to merge 2 commits intoTACC:masterfrom
AJVincelli:patch-1

Conversation

@AJVincelli
Copy link

Exclude ")" from the environment, which causes Launcher to fail when using GNU Screen on some clusters. Excluding the ")" fixes the issue for me.

Exclude ")" from the environment, which causes Launcher to fail when using GNU Screen on some clusters
@AJVincelli
Copy link
Author

@siliu-tacc @lwilson I have never done a Pull Request before, I apologize if I haven't done it right. Basically, when I use GNU Screen on some clusters, one of Screen's environmental variables includes a ")" and causes Launcher to fail. (I mentioned this behavior in Issue #63.) I just added -e ")" to the pass_env file, and this fixes the issue for me. Hopefully it's a tiny fix for review! Thanks!

@AJVincelli
Copy link
Author

Hm, actually my fix above might not work in all cases... Hold on while I check into this...

Excluded TERMCAP and its tabbed ($'\t') variables, which causes Launcher to fail when using GNU Screen on some clusters
@AJVincelli
Copy link
Author

@siliu-tacc @lwilson I updated the fix to include all TERMCAP environment variables, which apparently can include an entire database of tabbed variables. Excluding all tabbed variables seems to clear all (and only) screen variables, and Launcher runs successfully. Maybe somebody else who experiences the error can try this fix to confirm that it works for them too?

@AJVincelli AJVincelli changed the title Exclude ")" environmental variable in pass_env Exclude GNU Screen environmental variables in pass_env Mar 8, 2021
@AJVincelli AJVincelli mentioned this pull request Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant