Hi Kevin, Your point is very good. Sorry it takes so long to get back to you. I created a github issue page to track this down:
https://github.com/dmtcp/dmtcp/issues/219 You're very welcome to join the discussion. Best, Jiajun On Mon, Oct 19, 2015 at 7:54 PM, Kevin Buckley < kevin.buckley.ecs.vuw.ac...@gmail.com> wrote: > There is one other thing that I've just remembered thinking about, Kapil, > > When the previous version of "dmtcp_launch" printed out its > "status/verbose: info by default, it showed an > > Exit on last client: 1 > > line, however, it' s not clear to me that you could affect that status > for the coordinator when implicitly creating one via "dmtcp_launch"? > > Similarly, the coordinator's other related option "exit-after-ckpt" > > --exit-on-last > Exit automatically when last client disconnects > --exit-after-ckpt > Exit automatically after checkpoint is created > > does not appear to be duplicated within "dmtcp_launch" either? > > Is that a "future feature" ? > > Kevin > > > ------------------------------------------------------------------------------ > _______________________________________________ > Dmtcp-forum mailing list > Dmtcp-forum@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dmtcp-forum >
------------------------------------------------------------------------------
_______________________________________________ Dmtcp-forum mailing list Dmtcp-forum@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dmtcp-forum