|
From: Xavier D. <xav...@gm...> - 2022-04-09 16:52:01
|
Hi Frank, 2 different kind of configuration should be distinguished: * module command configuration * modulefiles configuration Each kind of configuration follows the "traditional" configuration cascading approach you describe. What may disturb is that the rc files are evaluated each time the modulecmd.tcl script is run and as this script is run to initialize the module command, these global rc files may impact the initialization process. Historically, global rc files are able to call the module command, but I encourage people to only configure modulefiles in these rc files and use the initrc and collections to setup the module command and the default environment to load. Cheers, Xavier Le ven. 8 avr. 2022 à 16:27, Frank Thommen <f.t...@dk...> a écrit : > Dear all, > > coming from the Linux shell and Linux commands and services, I am > confused about the "configuration flow" in modules. I am used to a > clear hierarchy of configuration directives. They are normally applied > in the order > > central configuration (file) > -> user configuration (file) > -> commandline parameters > > Later directives (in most cases) have higher priority. In modules the > order (at least regarding $MODULEPATH, not sure about other > configurations, though) seems different: > > user configuration (file) > -> central configuration (file) > -> commandline parameters > > This comes unexpectedly when you are used to other tools. > > First question: Did I maybe misunderstand module's configuration mechanism? > > If not: Do you know what is/was the rationale to design the mechanism > this way? Of course after 30 years I'm not expecting this to change > :-), but I would like to understand it > > Cheers and thanks in advance, Frank > > > _______________________________________________ > Modules-interest mailing list > Mod...@li... > https://lists.sourceforge.net/lists/listinfo/modules-interest > |
