Re: [Dmtcp-forum] Checkpoint and die?

[Gene C. <ge...@cc...>]

Excellent.  I should have gone back and reviewed the options on
dmtcp_coordinator.  You caught me in the middle of something else.
    Let us know if you have any problem with this.
Best,
- Gene

On Thu, Feb 27, 2014 at 01:53:49PM -0700, Levi Morrison wrote:
> $ dmtcp_coordinator --exit-after-ckpt
> 
> Usage: dmtcp_coordinator [OPTIONS] [port]
> 
> Coordinates checkpoints between multiple processes.
> 
> 
> Options:
> 
>   -p, --port PORT_NUM (environment variable DMTCP_PORT)
> 
>       Port to listen on (default: 7779)
> 
>   --port-file filename
> 
>       File to write listener port number.
> 
>       (Useful with '--port 0', which is used to assign a random port)
> 
>   --ckptdir (environment variable DMTCP_CHECKPOINT_DIR):
> 
>       Directory to store dmtcp_restart_script.sh (default: ./)
> 
>   --tmpdir (environment variable DMTCP_TMPDIR):
> 
>       Directory to store temporary files (default: env var TMDPIR or /tmp)
> 
>   --exit-on-last
> 
>       Exit automatically when last client disconnects
> 
>   --daemon
> 
>       Run silently in the background after detaching from the parent
> process.
> 
>   -i, --interval (environment variable DMTCP_CHECKPOINT_INTERVAL):
> 
>       Time in seconds between automatic checkpoints
> 
>       (default: 0, disabled)
> 
>   --help:
> 
>       Print this message and exit.
> 
>   --version:
> 
>       Print version information and exit.
> 
> 
> COMMANDS:
> 
>       type '?<return>' at runtime for list
> 
> 
> Report bugs to: dmt...@li...
> 
> DMTCP home page: <http://dmtcp.sourceforge.net>
> ----
> 
> So it seems the --exit-after-ckpt option won't work. Initial tests indicate
> that dmtcp_command -xc will work.