Am 06.12.2011 um 12:23 schrieb Ed Spittles: > Hi Reuti > thanks anyway. > > I agree, passing such a lot of information in the environment doesn't seem > like a good idea - of course, so long as it works someone will try it, and > then some day the problem space changes and it no longer works. I know this > works with LSF, or at least that LSF has a much higher limit. > > To answer an earlier query, I'm not sure how large this particular > configuration information might become - it's a list of files - 100k > characters would probably be enough.
This can also be a problem in bash on its own. Sometimes an `rm -rf *` won't work, as there are too many files in the directory and you have to delete it in bunches by feeding a couple of them to `rm -rf` by `xargs` in several loops. Would it be an option to name the files by something like a regular expression, which you parse in the jobscript to select the files? -- Reuti NB: Another option could be not to specify the list of files as assignment to a variable to -v, but to specify it after the name of the jobscript and read it then in the jobscript as $1. There you can get longer entries. > In all likelihood, we can find a way to use a file, although doing it with > minimal change to existing scripts and programs is the challenge. (It may be > that the work has been done while I was off-air.) > > Cheers > Ed > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
