Yes, it does appear that if an env variable is in excess of 9990 characters, the job environment seems somehow to be corrupted at the prolog level.
I created three large variables, and each was fine until the individual size of each exceeded 9990 chars. Submission cli: qsub -N largevarcheck -cwd -V ./t2.sh -or- qsub -N largevarcheck -cwd -V -b y ./t2.sh Tested: soge 8.1.3 rh6.3 64bit -Ed -----Original Message----- From: Ed Lauzier [mailto:[email protected]] Sent: Saturday, August 3, 2013 11:27 AM To: [email protected], [email protected] Subject: Re: [gridengine users] variable getting truncated in soge8.1.3 and OGS 2011.11p1 Did some digging..... with a prolog script like so..... env > /tmparea/prolog.out.txt The output looks like it is corrupted. The variable is fragmented into large pieces in the output - not sure if the command env is having issues or not.... I will see how large a consistent variable I can obtain. Currently, when echoing the variable in prolog, it's count is 9990 with an input size of 48895. -Ed -----Original Message----- From: Ed Lauzier [mailto:[email protected]] Sent: Saturday, August 3, 2013 02:25 AM To: [email protected], [email protected] Subject: [gridengine users] variable getting truncated in soge8.1.3 and OGS 2011.11p1 Hi, I'm testing the following: On soge 8.1.3 and OGS 2011.11p1 ( RHEL 6.3 64bit ) 1. create an env variable 48895 chars in size. ( chars 0-9 and "/"s only ) 2. qrsh -cwd -V works 3. qsub -cwd -V does not work ( truncates to 9990 chars ) The above numbered items works on SGE 6.2u5 for both qrsh and qsub. ( RHEL 5.3 64bit ) The reference seems to show that there may be an issue with the way a similar issue was patched by Sun in the past. http://gridengine.org/pipermail/users/2011-December/002113.html Anyone heard of this issue or a similar issue and if you have, can you point me to the appropriate threads? Thanks, Ed
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
