Question about module load

[Jonathan T. <jtu...@lu...>]

We are introducing linux machines to our solaris environment.  What we are
doing is setting up a compute farm(LSF) of servers running RedHat 7.2.
We have 2 issues in doing this:

Issue 1
-------
Because all of our tools do not run under linux, our modulefiles contain a
case statement, which determines the OS, and loads the appropriate
binaries(if they exist).  Iin the case of tools that do not run under
linux, I echo a statement to the window, stating that the tool is
unsupported under linux.  The problem, is that because that case of the
case statement was resolved, that modulefile shows up when we do a 'module
list' command.  Is there any sort of "trap" which would allow me to
control whether the "module list" gets updated if this type of case
resolves, and there is nothing to set up?  I don't want to load something
that doesn't exist.


Issue 2
-------
Is anyone out there running LSF and Modulefiles?  If so, have you noticed
that the aliases that you set in the modulefiles using the "set-alias"
command, don't get propagated when submiting a job to LSF?  This happens
in Solaris & Linux.  Is there any way to get around this?

Any help would be appreciated.

Thanks,

Jon