On 19 October 2015 at 15:24, Kevin Buckley <[email protected]> wrote:
> 1) I am no longer seeing any basic "info" from the launcher > 2) I get a "ckpt dump" but no restart script (or convenience link) > > Maybe more has changed than just the "interval fix"? I'll keep looking. Ignore (2). There was a 2.4.1 dmtcp_coordinator hanging around, backgrounded, from Friday, so I guess my first 2.4.2 test ended up communicating with that. Once I've binned that, I can see that the launcher has fired up its own dmtcp_coordinator, however the info telling you what's it's doing is still not there. More importantly, the automatic checkpointing at intervals seems to work: ======================================= [term1]$ DMTCP_CHECKPOINT_INTERVAL=90 dmtcp_launch ./dmtcp1 1 2 3 4 5 6 7 8 9 ... time passes ... [term2]$ ls -otr -rw------- 1 user1 2874405 Oct 19 15:36 ckpt_dmtcp1_420d2b52e1fa2651-40000-562456c5.dmtcp -rwxr--r-- 1 user1 6353 Oct 19 15:36 dmtcp_restart_script_420d2b52e1fa2651-40000-562456c4.sh* lrwxrwxrwx 1 user1 114 Oct 19 15:36 dmtcp_restart_script.sh -> /path/to/file* [term2]$ cp ckpt_dmtcp1_420d2b52e1fa2651-40000-562456c5.dmtcp dmtcp_restart_scr* Old/ [term1]$ ... time pases ... [term2]$ ls -otr ... -rw------- 1 user1 2874497 Oct 19 15:39 ckpt_dmtcp1_420d2b52e1fa2651-40000-562456c5.dmtcp -rwxr--r-- 1 user1 6353 Oct 19 15:39 dmtcp_restart_script_420d2b52e1fa2651-40000-562456c4.sh* lrwxrwxrwx 1 user1 114 Oct 19 15:39 dmtcp_restart_script.sh -> /path/tofile/* [term1]$ ... time pases ... 133 134 135 136 137 138 139 140 141 ^C [term1]$ ./dmtcp_restart_script.sh 136 137 138 ^C [term1]$ rm ckpt_dmtcp1_* dmtcp_restart_script* [term2]$ cp Old/ckpt_dmtcp1* Old/dmtcp_restart_script.sh . [term1]$ ./dmtcp_restart_script.sh 91 92 ^C ======================================= which, I guess, is QED. ------------------------------------------------------------------------------ _______________________________________________ Dmtcp-forum mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
