|
From: R.K. O. <rk...@ow...> - 2016-08-17 20:07:40
|
Hello Scott: Modules wasn't designed to handle full paths to modulefiles. Generally, you want to load the use.own module and place any of your own modules in ~/privatemodules/ and have the modulecmd locate them from there. Or append/prepend your own path for these modules to MODULES_PATH. R.K. Owen On Wed, Aug 17, 2016 at 12:59 PM, Scott Johnson <sc...@si...> wrote: > What could be the reason for `module unload` silently refusing to unload a > module? Strangely, `module purge` does unload it. > > AFAICT the unload command is not executing the modulefile's tcl at all. > > scottj@i1:~$ module list > No Modulefiles Currently Loaded. > scottj@i1:~$ module load /home/scottj/sifive-modules.good/sifive.localgit > scottj@i1:~$ module list > Currently Loaded Modulefiles: > 1) /home/scottj/sifive-modules.good/sifive.localgit > scottj@i1:~$ module unload /home/scottj/sifive-modules.good/sifive.localgit > scottj@i1:~$ module list > Currently Loaded Modulefiles: > 1) /home/scottj/sifive-modules.good/sifive.localgit > scottj@i1:~$ module purge > scottj@i1:~$ module list > No Modulefiles Currently Loaded. > > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Modules-interest mailing list > Mod...@li... > https://lists.sourceforge.net/lists/listinfo/modules-interest > > |
