I have a use case where I'd like to start up multiple copies, on the same
host, of a checkpoint which has been performed with --checkpoint-open-files
enabled.
One issue (perhaps there are others :->) is that as far as I can tell dmtcp
wants to restore files to their original absolute locations (example
/tmp/foo/bar.txt) and there is currently not any way to control this. Is
this true?
If so, I'd envision writing a small plugin which would, for example, allow
the user to specify a unique prefix which would be prepended to all file
locations (including new files created, previous files taken using
--checkpoint-open-files, etc).
Any pitfalls I am missing?
I would also expect this feature to support a use case where, for whatever
reason, you relocate a checkpoint to a target system and can no longer
write to the original file locations (due to permissions or filesystem
structure changes), but it is important to reuse this checkpoint.
I would appreciate any feedback.
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
