Hi Nausca,
You'll now find my analysis at
https://github.com/dmtcp/dmtcp/issues/245
The short story is that the --no-coordinator flag only supports
a single process (since the coordinator is then built into
the target user process). The tcsh application is calling
fork() (as one would expect). Our error message is a bad one,
and we'll improve it.
The short story is that tcsh wants to call fork(), and in that case,
only a separate dmtcp_coordinator process is supported (which then sends
checkpoint requests to the various user processes).
Best wishes,
- Gene
On Wed, Nov 25, 2015 at 02:45:14AM +0000, Nausca Hsu wrote:
> Hi,
> I am trying latest 2.4.2 version
> I use
> dmtcp_launch -no-coordinator -interval 60 tcsh
> For a test, dmtcp_launch will assert at createNewConnectionBeforeFork,
> coordinatorapi.cpp:562.
> Anybody every use the -no-coordinator successfully?
>
> Thanks.
> Nausca.
> _______________________________________________
> Dmtcp-forum mailing list
> Dmtcp-forum@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Dmtcp-forum mailing list
Dmtcp-forum@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
