Closed boegel closed 7 years ago
i also tested the patch on node2160, no apps access anymore, but /etc/modules/vsc is still scanned (but that is less of an issue). iguess /etc/modules/vsc is not in the cache?
@stdweird If you do a module load cluster
, it will still re-evaluate all cluster
modules to check which one is the default, I think (it doesn't decide the default based on the cache).
I may be wrong here though... Maybe @rtmclay can clarify?
Anyway, since that bit is local disk, that's really not a problem imho.
@boegel how are "cluster" modules different from other modules? anyway, i just saw this in the strace, and wanted to report it.
We deploy those via an RPM (see our vsc-cluster-modules
repo)
@boegel and? you mean there's no update cache in the rpm post script? but the cron job should pick this up, no?
@stdweird The cron job starts from /etc/modulefiles/vsc
, and then discovers all other modules through the paths that the cluster
modules prepend to $MODULEPATH
.
The cluster
modules themselves are also in the Lmod cache though (see grep modulefiles /apps/gent/lmodcache/spiderT.lua
), it's scanning them for another reason (my best guess is to check which of them is the default).
@boegel ok, thanks.
PR https://github.com/TACC/Lmod/pull/300 was merged, but no new version was tagged yet. I see no reason to wait for that though...
Our integration tests pass with this installed: