You can drop the init/csh and init/sh initialization scripts into /etc/profile.d/ renaming them to module.csh and respectively, and when a user logs in then they will have the alias created for them automatically.

I crafted add.modules script because the place I worked at at the time the sysadmins didn't want changes to the system /etc files, hence a script to make it easier for users to add the capability to their dot files.  However, I prefer the /etc/profile.d/ and the like way of doing things.

You should add /etc/skel/.module with
module load null

so users can have the same modules regardless of the shell they use.

   R.K. Owen

On Thu, Jun 30, 2011 at 10:13 AM, Doug Hensel <> wrote:

I am a new user trying to deply Environment Modules in a large setting
(over 100 users). I have a mix of bash and csh (and who knows what
else). I do not want to modify each individuals home environment. Can
I use this tool to create a module that each person can run ? by
calling modulecmd ? I see some example in the documentation, but it
just shows how to start from scratch and modify a users home
directory, and then get started. I want to bypass modifying the user
env. I am working with the C compiled version. Compiled on a Redhat AE
system, 64-bit.



All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
Modules-interest mailing list