Hi,
I am working on making my application dmtcp aware (using dmtcp 1.2.6) because
of some troublesome things I won't detail here. The idea is that I use the
preCheckpoint hook to save some information about my application and then
destroy troublesome items. During the postCheckpoint/postRestart hook
functions I then recreate the troublesome items and restore them from the saved
state. The obvious (at least to me) place to save the state is in the
checkpoint directory. The problem I'm running into is that the checkpoint
directory stored in the local status structure returned by
dmtcpGetLocalStatus() is different between the preCheckpoint and postCheckpoint
hook functions. It appears the checkpoint count is incremented between the
preCheckpoint and postCheckpoint hooks. Is this by design? I can work around
this, but it's tedious and makes me wonder if there is a reason for doing
things this way or if I may be doing something in an undesirable way.
Thanks,
John Fredine
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dmtcp-forum mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum