|
From: Xavier D. <xav...@gm...> - 2022-01-16 07:22:37
|
This terminology "Modules magic cookie" is there since a long time, if you feel that this is too awkward for present times, maybe we could rebrand that into "magic header" or "Modules header" abbreviated "mheader" so to have a "mheader_check" option. I can change mcookie_check option name as 5.1 is not released yet. For mcookie_version_check I will need to wait for 6.0 (in 2 to 4 years) to change the name of this existing option. What is your opinion on that? Regards, Xavier Le sam. 15 janv. 2022 à 17:29, Paul Markfort <pau...@gm...> a écrit : > > Maybe: module_marker_check > > However, there is already an "mcookie_version_check" setting that is > closely related (so mcookie_check seems quite appropriate). > > Also, I should point out that mcookie is a contraction of Magic Cookie > (that I have seen used in non module contexts - there is even an "mcookie" > command in linux: mcookie - generate magic cookies for xauth). > > > On 2022-01-15 07:57 AM, Sternberg, Michael G. via Modules-interest wrote: > > Xavier, > > > > This is a great development! Dependency handling systems for HPC > application deployment, like Spack, have made for some pretty deep and > complex modulefile trees as of late. > > > > May I suggest a name change for the feature, though, if it isn't already > committed? > > > > I ask because the term "cookie" could be misunderstood, as it has > connotations with communication protocols, notably HTTP. Following > convention, a more grokable name for the feature would be "[file ]magic" or > "[file ]signature" – see > https://en.wikipedia.org/wiki/List_of_file_signatures . The page even > includes "#%Module" in its list of examples. > > > > > > Best wishes, > > -- > > Michael Sternberg, Ph.D., Principal Scientific Computing Administrator > > Center for Nanoscale Materials, Argonne National Laboratory > > > > > > On Jan 14, 2022, at 00:43, Xavier Delaruelle < > xav...@gm...> wrote: > > Hello All, > > > > Modules 5.1 work is ongoing. A new configuration option, mcookie_check, > is introduced to skip the verification of each file in modulepath > directories to determine if they are modulefiles or not. When this option > is set to `eval`, file checks only occur when an attempt is made to > evaluate these files, not when listing available modules. So if you fully > control what files are saved under the modulepath directories you could get > a nice speed improvement, especially for commands like 'module avail': > > > > > https://modules.readthedocs.io/en/latest/MIGRATING.html#reducing-number-of-i-o-operations > > > > A full cookbook recipe is also available to describe the features of > Modules that help to reduce the I/O load of walking through the available > modulefiles: > > > > > https://modules.readthedocs.io/en/latest/cookbook/reduce-io-load.html#reduce-io-load > > > > Regards, > > Xavier > > > > > > > > _______________________________________________ > > Modules-interest mailing list > > Mod...@li... > > https://lists.sourceforge.net/lists/listinfo/modules-interest > > > > -- > -------------------------------------------------------- > The views and opinions expressed above are strictly > those of the author(s). The content of this message has > not been reviewed nor approved by any entity whatsoever. > -------------------------------------------------------- > Paul FM Info: http://paulfm.com/~paulfm/ > -------------------------------------------------------- > > > _______________________________________________ > Modules-interest mailing list > Mod...@li... > https://lists.sourceforge.net/lists/listinfo/modules-interest > |
