Re: [Lmod-users] Disabling automatic unload/load when a module with an other version is already charged

[Lebouc L. (CS SI) <Lis...@cn...>]

Perfect !

Thank you !!!!
Lise


De : Kenneth Hoste [mailto:ken...@ug...]
Envoyé : jeudi 15 décembre 2016 14:47
À : lmo...@li...
Objet : Re: [Lmod-users] Disabling automatic unload/load when a module with an other version is already charged

Hi Lise,
On 15/12/16 13:54, Lebouc Lise (CS SI) wrote:
Hi everybody !

There is an automatic unload/load when a module with an other version is already charged. Is it possible to disabling it?

For example, if I have 3 modules like :
   1) moduleA/1.0
   2) moduleA/2.0
   3) moduleB/1.0 which depend on moduleA/2.0 : load ("moduleA/2.0")

Actually if I load moduleA/1.0 then moduleB/1.0, moduleA/1.0 is unload and the moduleA/2.0 is load. There is a message :
The following have been reloaded with a version change:
  1) moduleA/1.0 => moduleA/2.0

Is it possible to prohibit the load of moduleA/2.0 because moduleA/1.0 is already loaded?

I tried with conflict and family but it's seem work only this different name of module.

You can configure Lmod not to print an error message rather than doing the auto-swap, either by passing --with-disableNameAutoSwap=yes when you're configuring the Lmod build/install, or by defining $LMOD_DISABLE_SAME_NAME_AUTOSWAP using "export LMOD_DISABLE_SAME_NAME_AUTOSWAP=yes".


regards,

Kenneth