From: Jason A. <ja...@cs...> - 2011-02-19 19:46:31
|
You can read (but not write) the filename of the checkpoint through dmtcpGetLocalStatus()->checkpointFilename On Sat, Feb 19, 2011 at 2:42 PM, Kapil Arya <ka...@cc...> wrote: >> My main interest is a backup against failures for long-running >> simulations, >> which are of a trivial parallel nature (i.e., multiple simultations with >> no >> interaction between processes). >> >> There might be 100s of simulation results in the same directory. I would >> want >> to at least be able to get the name of the checkpoint files so I would >> know >> which to restart - but more important I'd probably want my script to >> automatically remove checkpoint files when jobs complete - so it needs to >> know >> the names. Being able to set the name I think is a nice enhancement, but >> getting the name seems required. > > Okay, so I will try to spare some cycles to get this feature into DMTCP > sometime over this weekend. Will write you back once I have committed the > code to svn. > --Kapil > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Dmtcp-forum mailing list > Dmt...@li... > https://lists.sourceforge.net/lists/listinfo/dmtcp-forum > > |