[env-switcher-devel] [ env-switcher-Bugs-559634 ] Need to reset env vars

[<no...@so...>]

Bugs item #559634, was opened at 2002-05-23 07:07
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=465044&aid=559634&group_id=51915

Category: modules RPM
Group: None
>Status: Closed
>Resolution: Duplicate
Priority: 5
Submitted By: Jeff Squyres (jsquyres)
Assigned to: Jeff Squyres (jsquyres)
Summary: Need to reset env vars 

Initial Comment:
If one logs in as root and su's to another user that
also uses modules, you'll get warnings that you can't
write to ~root/.modulesbeginenv.  This seems to be
because the $_MODULEBEGINENV_ environment variable is
not reset when we change to a new user.

The same kind of thing happens if you login as a normal
user with a $HOME on a node with an NFS filesystem that
has no root privlidges, and you "su" to root -- root
cannot write to the user's $HOME/.modulesbeginenv.

It seems that there are several variables that should
probably be reset/unset when we change to a new user. 
So in addition to $MODULE_OSCAR, do we also need a
$MODULE_OSCAR_USER that we maintain the username of the
current user, and if whoami returns a different string
than what is in $MODULE_OSCAR_USER, then we reset all
the module env vars and re-do all the setup?

Something along these lines is worth looking into.

----------------------------------------------------------------------

>Comment By: Jeff Squyres (jsquyres)
Date: 2002-05-23 22:21

Message:
Logged In: YES 
user_id=11722

Fixed in CVS.

Now, if the shell or the user changes, the
profile.d/00-modules.* shell script will detect this and
force the modules package to do a hard reset by unsetting
all the modules-related environment variables.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=465044&aid=559634&group_id=51915