Description
Not so much an issue: more a trying to work out if I can do
something or not.
In our HPE/Cray environment, users who login get a default
set of modules, however, the way in which the default set gets
loaded, sees one "top-level" module, that does get shown as
the default, denoted by a (D)
when one does a module avail
,
not listed as being Loaded, so denoted by an (L)
, nor showing
in the list seen when doing an initial module list
.
I think of it as a kind of a "halfway house": by virtue of being there,
you know you are on the right road, but you become aware that you
still haven't quite got there.
Somewhat bizzarely, if one swaps away from the "not-loaded default"
but then swaps back to it, the "default" then shows as (L,D)
in a
module avail
and also now appears in a module list
.
What I'd like to do, so as to reduce any confusion that might arise
from a simple inspection of the login environment, is to FORCE
the `(L)' onto that "top-level" module.
Is that even possible?
My guess is "No", but those who know the innards might know
"better" - assuming that that ability does make things better!