[torquedev] epilogue.parallel in 2.0.0

Marcus R. Epperson mrepper at sandia.gov
Mon May 1 17:15:52 MDT 2006


>From what I can tell, these are the changes for epilogue.parallel that went into 2.1.0.  Could they be included in the next 2.0.0 release as well?  (assuming there are plans for another 2.0.0 release)

This functionality is very useful and it seems to work fine with 2.0.0p8 based on the testing I've done.

Thanks,
-Marcus Epperson

-------------- next part --------------
--- torque-2.0.0p8/src/resmom/catch_child.c	2006-01-27 11:42:05.000000000 -0700
+++ torque-2.1.0p0-snap.200603221901/src/resmom/catch_child.c	2006-03-21 21:22:49.000000000 -0700
@@ -122,6 +122,8 @@
 
 extern char		*path_epilog;
 extern char             *path_epiloguser;
+extern char             *path_epilogp;
+extern char             *path_epiloguserp;
 extern char		*path_jobs;
 extern unsigned int	default_server_port;
 extern list_head	svr_alljobs, mom_polljobs;
@@ -567,6 +569,30 @@ void scan_for_exiting()
       if (ptask != NULL)
         continue;
    
+      if ((pjob->ji_wattr[(int)JOB_ATR_interactive].at_flags & ATR_VFLAG_SET) &&
+           pjob->ji_wattr[(int)JOB_ATR_interactive].at_val.at_long) 
+        {
+        if (run_pelog(PE_EPILOG,path_epilogp,pjob,PE_IO_TYPE_NULL) != 0)
+          {
+          log_err(-1,id,"parallel epilog failed");
+          }
+        if (run_pelog(PE_EPILOGUSER,path_epiloguserp,pjob,PE_IO_TYPE_NULL) != 0)
+          {
+          log_err(-1,id,"user parallel epilog failed");
+          }
+        }
+      else
+        {
+        if (run_pelog(PE_EPILOG,path_epilogp,pjob,PE_IO_TYPE_STD) != 0)
+          {
+          log_err(-1,id,"parallel epilog failed");
+          }
+        if (run_pelog(PE_EPILOGUSER,path_epiloguserp,pjob,PE_IO_TYPE_STD) != 0)
+          {
+          log_err(-1,id,"user parallel epilog failed");
+          }
+        }
+                                   
       /*
       ** No tasks running ... format and send a
       ** reply to the mother superior and get rid of


More information about the torquedev mailing list