p.s Now I see that when using sge_request file I only get the output to stdout in the client but not to the master log file. I suppose it is related to what Reuti explained previously, using sge_request the jsv runs as a client side JSV (qsub child).
The ideal would be to get the output in both logfile and client stdout, anyways I prefer the output to the client stdout because I want that my users get noticed about the reason why their jobs are rejected or which modifications are done by the jsv script. regards, pablo. 2013/11/13 Pablo Escobar <pescobar...@gmail.com> > Hi Arnau, I have just done this 1min ago :) > > when using jsv_url and calling jsv_log_info() function in the perl jsv I > was getting no output to stdout in the client machine, I was only getting > the output of jsv_log_info() in the master log. > > After this workaround of using sge_request file instead of global jsv_url > config, jsv_log_info() function shows the output correctly in the client's > stdout > > thanks! > Pablo. > > > 2013/11/13 Arnau Bria <listsar...@gmail.com> > >> Hi Pablo, >> >> I did add >> >> -jsv /usr/local/bin/jsv.pl >> >> to jse_request because I also had problems with jsv_url parram. >> >> Cheers, >> Arnau >> _______________________________________________ >> users mailing list >> users@gridengine.org >> https://gridengine.org/mailman/listinfo/users >> > >
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
