If I'm being pedantic about the option "--checkpoint-open-files", this
means that the subject case is not handled.

True statement?

In other words, often processes will create a file, write some stuff, and
close it.  It would be nice if DMTCP had an option to bookkeep those files
and store them in the `ckpt*_files` folder along with contents of open
files at the checkpoint time.

This allows a more precise capture of the process state and supporting
files which may be required for migrating said process to other machines,
etc.

This seems doable, with just a simple array to handle previously opened
files, and an option to copy those files to ckpt_files on checkpoint, and
to restore them to previous location on restart (of course included
pathvirt functionality as well ;->).

Thoughts? Comments?  Edge cases?  Already supported and I missed it?


Thanks,
Kyle Harrigan
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Dmtcp-forum mailing list
Dmtcp-forum@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum

Reply via email to