On 29/09/14 15:28, Christopher Samuel wrote: > B) If you update a compute node when there are jobs queued under the > previous bash then they will fail when they run there (also cannot find > modules, even though a prologue of ours sets BASH_ENV to force the env > vars to get set).
Well embarrassingly it turns out that the fact that BASH_ENV didn't work was a typo on our part. :-( -echo export BASH_ENV=/etc/profile.d/modules.sh +echo export BASH_ENV=/etc/profile.d/module.sh Found when trying to debug why a user who had tcsh as his default shell couldn't run jobs after the bash upgrade (his job script had #!/bin/sh). I'll see if I can find a way to retest with an older bash. cheers, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
