From frank.thommen at embl-heidelberg.de Tue May 21 17:20:57 2013 From: frank.thommen at embl-heidelberg.de (Frank Thommen) Date: Tue, 21 May 2013 17:20:57 +0200 Subject: [op-sepp] Inheriting the current environment into the SEPP compile shell Message-ID: <519B90D9.4010308@embl-heidelberg.de> Hi, seppadm execs a shell (compile shell) w/o inheriting any environment variables. This creates problems on some buildhosts which require a specific environment ($MODULESPATH, $MODULESHOME) which should be inherited from the standard login environment. These variables are not always the same on all buildhosts. Where is the "cleanup" of the environment variables done and how can we disable it? SaneShell() doesn't seem to remove any existing variables, just set some. On the other hand, custom variables defined in "compile env" are ignored. Cheers frank -- Frank Thommen - Structures IT Management and Support - EMBL Heidelberg frank.thommen at embl-heidelberg.de - +49 6221 387 8353 From tobi at oetiker.ch Tue May 21 18:00:15 2013 From: tobi at oetiker.ch (Tobias Oetiker) Date: Tue, 21 May 2013 18:00:15 +0200 (CEST) Subject: [op-sepp] Inheriting the current environment into the SEPP compile shell In-Reply-To: <519B90D9.4010308@embl-heidelberg.de> References: <519B90D9.4010308@embl-heidelberg.de> Message-ID: Hi Frank, Today Frank Thommen wrote: > Hi, > > seppadm execs a shell (compile shell) w/o inheriting any environment > variables. This creates problems on some buildhosts which require a > specific environment ($MODULESPATH, $MODULESHOME) which should be > inherited from the standard login environment. These variables are not > always the same on all buildhosts. > > Where is the "cleanup" of the environment variables done and how can we > disable it? SaneShell() doesn't seem to remove any existing variables, > just set some. On the other hand, custom variables defined in "compile > env" are ignored. that would be the places where I would have looked ... also a /usr/sepp/conf/.cshrc file cheers tobi > > Cheers > frank > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900 From frank.thommen at embl-heidelberg.de Tue May 21 18:25:06 2013 From: frank.thommen at embl-heidelberg.de (Frank Thommen) Date: Tue, 21 May 2013 18:25:06 +0200 Subject: [op-sepp] Inheriting the current environment into the SEPP compile shell In-Reply-To: References: <519B90D9.4010308@embl-heidelberg.de> Message-ID: <519B9FE2.1000005@embl-heidelberg.de> Hi Tobi, >> seppadm execs a shell (compile shell) w/o inheriting any environment >> variables. This creates problems on some buildhosts which require a >> specific environment ($MODULESPATH, $MODULESHOME) which should be >> inherited from the standard login environment. These variables are not >> always the same on all buildhosts. >> >> Where is the "cleanup" of the environment variables done and how can we >> disable it? SaneShell() doesn't seem to remove any existing variables, >> just set some. On the other hand, custom variables defined in "compile >> env" are ignored. > > that would be the places where I would have looked ... also a > /usr/sepp/conf/.cshrc file /usr/sepp/conf/.cshrc was it: unsetenv * Thx frank