You can decide to hide a module based on it's full name, short name or
path to the module file. So yes.
Ward
On 28-06-17 09:55, Alan O'Cais wrote:
> So you're saying you can select to hide all modules called
> Core/Compiler/MPI (in a HMNS) which you pick up
> from $EB_GLOBAL_PREFIX/modules/all
So you're saying you can select to hide all modules called
Core/Compiler/MPI (in a HMNS) which you pick up
from $EB_GLOBAL_PREFIX/modules/all ?
On 28 June 2017 at 09:46, Kenneth Hoste wrote:
> Hi Davide & Miguel,
>
> With Lmod, there's another option: you can selective
Hi Davide & Miguel,
With Lmod, there's another option: you can selective hide modules from
users, without breaking existing 'module load' commands, to actively
discourage them from using old installations for example.
This can be done in various ways, e.g. by putting .modulerc files in
Hello Davide,
On 28 Jun 2017 02:43, "Vanzo, Davide" wrote:
So, I gave it a try and it works fine.
The only annoyance (since it is more a matter of style) is that once I add
the $EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH, Lmod output for
"module avail" gets
So, I gave it a try and it works fine.
The only annoyance (since it is more a matter of style) is that once I add the
$EB_GLOBAL_PREFIX/modules/all to the $MODULEPATH, Lmod output for "module
avail" gets pretty crowded.
--
Davide Vanzo, PhD
Application Developer
Advanced Computing Center for
On 27/06/17 15:42, Alan O'Cais wrote:
That is a neat trick with the sourcepaths that I will try out today.
I have to credit boegel, he told me about it, I had simply assumed that
would not work :)
I think there is a bit more to a user install space than what's been
mentioned when you
That is a neat trick with the sourcepaths that I will try out today.
I think there is a bit more to a user install space than what's been mentioned
when you have a HMNS, see
https://github.com/hpcugent/easybuild-framework/issues/2143
On 27 June 2017 at 03:09, Fotis Georgatos
Hi Miguel,
Yeap! i’d also fully applause this approach, it is very similar to what we’ve
been doing since 2012!
- $MODULEPATH can include both global and local builds, you just need to decide
their exact order
* fyi. recent versions of Lmod have in ./contrib a pair of use.own.eb
Hello Davide,
I also had doubts initially because of what you mention and also using
global source paths, but this works for us:
- create and manage a cluster-wide software stack with an easybuild user,
using EASYBUILD_PREFIX=$EB_GLOBAL_PREFIX
- for normal users
- set
Hello guys,
We would like to allow users to install software locally in their home
directories via EB. Is there a way to configure EB to install the software and
the modules in a local directory if the user is just a regular user but allow a
subset of users (admins) to install directly in the
10 matches
Mail list logo