Thanks, Rohan.

I think I understand now the issue. Yes, dmtcp_coordinator was not started from 
the place checkpoint was initiated. After fixing that, it worked.

My assumption was that dmtcp_coordinator is a daemon which can be started 
anywhere and keeps running, and it will know if checkpoint directory is changed 
via API by any of worker threads.

Apparently, it works differently as you stated. Is there a specific reason why 
coordinator cannot access this directory to write restart script even though 
the dmtcp checkpoint itself is written already in that directory?

-ashutosh

From: Rohan [mailto:rohg...@ccs.neu.edu]
Sent: Tuesday, May 03, 2016 3:43 PM
To: Ashutosh Varma <ashutosh.va...@synopsys.com>
Cc: dmtcp-forum@lists.sourceforge.net
Subject: RE: [Dmtcp-forum] (strerror((*__errno_location ()))) = No such file or 
directory


You need to verify if the said directory exists relative to directory from 
which the coordinator is launched. My guess is that it doesn't exist.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Dmtcp-forum mailing list
Dmtcp-forum@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum

Reply via email to