Maybe an administrator made that file (or a program they were using to
edit the file created temp files like this). The error is because the
user does not have access to the file (which really makes me think some
other program did this).
It does not look like a file name that modules would create automatically.
On 6/24/15 1:18 PM, Michael Gooch wrote:
> 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.
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
>
>
>
> _______________________________________________
> 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.
I should not be considered an "AUTHORITY" on any subject.
---------------------------------------------------------------------
Paul FM Info: http://www.umn.edu/~paulfm/
---------------------------------------------------------------------
|