Hi Valeriu, Kenneth, On Nov 18, 2014, at 9:35 PM, Kenneth Hoste <[email protected]> wrote: > It may have something to do with the modules being loaded with the old > modulecmd binary (v3.1.6), and then manipulating/querying the state with the > latest version 3.2.10.
Or, perhaps there is something that tickles environment variables LOADEDMODULES and _LMFILES_; I’d suspect either shell init files or, fancy hooks living inside modulefiles themselves. I'd suggest a clean-fresh build of modulecmd, visible by a very restricted $PATH, if possible, done from a new clean account. That may help in differential debugging. cheers, F. -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
