Am 06.11.2014 um 18:57 schrieb Alex Chekholko: > On 11/6/14, 12:22 AM, William Hay wrote: >> On Wed, 5 Nov 2014 23:08:53 +0000 >> Alex Chekholko <ch...@stanford.edu> wrote: >> >>> So I have a bash env var called "BASH_FUNC_module()" and when the tcl >>> jsv tries to make a TCL variable with that name, it errors out because >>> of the parenthesis. I think this is a recent change in bash due to the >>> bash vulnerability fix and how bash functions are handled. >>> >>> As a workaround, we can tell users not to use the '-V' flag to qsub. >>> >>> What would I need to do to make the -V flag to qsub work again? >> >> You could write a wrapper around qsub that serialises all the functon >> definitions into a single variable and then removes >> them from the environment. You could then add a starter_method that >> unserialises the function definitions back into >> the environment before executing the job. >> > Aww, that sounds like a bunch of work. > > On the lmod mailing list, there was some discussion of whether it's a good > idea at all to allow users to pass arbitrary environment settings through. > > I added this to our docs for now: > > ##We strongly discourage users from exporting their environment onto the > compute node. > ##Doing this pretty much means the job is non-reproductible, > ##because all the required settings are not captured in the job script. > ## > ## pass the current environment variables > ##$ -V > ##
+1 Therefore I don't like it too. -- Reuti _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
