a user reported the following problem related to loading a module:
utility.c(2245):ERROR:50: Cannot open file
'/UCHC/HPC/Gooch/biotoolmodules/modulefiles/STAR/_STARtmp' for 'reading'
utility.c(2245):ERROR:50: Cannot open file
'/UCHC/HPC/Gooch/biotoolmodules/modulefiles/STAR/_STARtmp' for 'reading'
why would temporary files be getting created in the child path where the
file defining how to load the module resides? The users don't have write
access to that path, and yet they can load other modules with no problem.
I'm confused as to what is causing this.
|