https://bugzilla.suse.com/show_bug.cgi?id=1206957 https://bugzilla.suse.com/show_bug.cgi?id=1206957#c10 Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |eich@suse.com --- Comment #10 from Egbert Eich <eich@suse.com> --- (In reply to Ludwig Nussel from comment #5)

No it's not a duplicate. lmod is doing nasty things here and pollutes the shell environment via /etc/profile.d/lmod.sh. My strong advice would be not do that. Instead there could be eg. only something like an "lmod-activate" or "lmod-enter" alias that sources /usr/share/lmod/8.7.15/init/bash *on demand* rather than for each and every shell of each and every user.

This would break every existing job scripts for users. We cannot do this. 'module load' needs to work in a batch environment from inside shell scripts. This is why BASH_ENV is set. Also, it is expected that every (physical) user logging into a system with Lmod installed will actually need it. On non-HPC systems, the lua-lmod package should not be installed. We can mitigate the impact of having BASH_ENV set by delaying the offending operations - which have been added recently - until when the 'module' command is actually run. This should fix the issue for lessopen.sh and possibly any other non-interactive calls to bash. -- You are receiving this mail because: You are on the CC list for the bug.