I've been starting my executables with something like:
dmtcp_checkpoint --port 0 ./myprogram <filein 1>output 2>error
and restarting them with something like
./dmtcp_restart_script.sh --ckptdir ./
In 1.2.8, this worked fine. In particular, on restart,
standard output (the file output, above) would be truncated back
to the correct location and further standard output would end up
there, despite my not specifying "1>output" on the restart. That
this worked was a bit surprising, but very convenient.
In 2.0, this no longer works. On restart, the output file is
ignored and standard output goes to standard output.
Is there a way to get the old behavior, or something similar out
of 2.0? I'd be okay with passing something like
"--put-stdout-here=output" to dmtcp_checkpoint and/or
dmtcp_restart_script.sh. If this functionality isn't in 2.0,
could it be?
--
Alan De Smet Center for High Throughput Computing
[email protected] http://chtc.cs.wisc.edu
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Dmtcp-forum mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
