Hi, Am 10.12.2011 um 10:01 schrieb mahbube rustaee:
> some slicker users submit jobs and save needed output , then run qdel and > delete the job on sge. > there isn't any record accounting for such jobs whereas user has saved > outputs. correct. The output is set on a user level, and they can redirect the output in the shell script to any location they like. SGE can't trace this (well, the shepherd would have to catch all file access operations and record them). If they include the number of the job in the output, they can use the `find` command to scan for a filename containing it. If you refer just to the settings of "-o path", you could use a prolog to save this information to a directory like /var/spool/sge/context/$JOB_ID (we use the name context as we want to save some of the context settings of the submission). Then in a mail-wrapper to SGE you can scan for this information, and add the used paths to the generated eMail. Important in your case are the values of $SGE_STDOUT_PATH and $SGE_STDERR_PATH Another option could be to generate an eMail only in case of a `qdel`, hence by a terminate_method where you can still access this information before sending any signals to the job. -- Reuti > Any suggestion to prevent mentioned senario? > > Thx > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
