Hi, Am 01.12.2011 um 22:37 schrieb Ed Spittles:
> Hi > (Sorry for the long delay - my filters mis-categorised this thread, and > we've worked around the problem by avoiding abusing the environment so much) > > On 7 October 2011 01:32, Reuti <[email protected]> wrote: > > yes, there is a limit. > > Please could you indicate where in the source this is? unfortunately it's not just one entry somewhere which could easily be increased AFAICS. First the -v option is split in bunches of 10k (not K) and recorded per variable (i.e., a longer name of the variable leads to less characters left for the content). Later on a similar string is used to read the environment file. It might be personal taste: but if I would face such a setup I would look in a different way to distribute the information to the job. 10k is not very handy on the command line. -- Reuti > Even changing the environment file by hand as I suggested in: > > http://gridengine.org/pipermail/users/2011-September/001638.html > > won't help here. > > This is just one variable with a long text or so? Or is it an awk script > inside? > > It is just one variable > > > BTW: For a job context, there is no such limit: > > http://gridengine.org/pipermail/users/2011-September/001630.html > > Thanks: it just might be possible to stash the information, using our qsub > wrapper, and perhaps also to retrieve it before the job proper executes. > > > -- Reuti > > > Cheers > > Ed _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
