From: Kapil A. <ka...@cc...> - 2013-10-22 20:45:10
|
Thanks for the information Alexandre. Kapil On Tue, Oct 22, 2013 at 11:54 AM, Alexandre Gravier <al....@gm...>wrote: > Dear Serge and Kapil, it appears that there is no problem with LXC or > DMTCP; the whole story is due to an unification fs issue. > > Thanks again for your help. > > Regards, > Alexandre > > > On Thu, Oct 10, 2013 at 10:24 AM, Alexandre Gravier <al....@gm...>wrote: > >> Hi Serge. Thanks for double-checking. I'm just a user of that system, >> so I need to contact the sysadmins about that. I (or they) will get >> back to you if they are willing to cooperate. >> >> On Thu, Oct 10, 2013 at 1:19 AM, Serge Hallyn <ser...@ub...> >> wrote: >> > Quoting Alexandre Gravier (al....@gm...): >> >> Hi Kapil, >> >> >> >> Thank you for your insights. You are spot on. The /proc/<PID>/maps of >> >> the processes I try to serialise with DMTCP contain the exact list of >> >> incorrect filepaths that DMTCP spits out. >> > >> > I can't reproduce that. /proc/self/maps inside a container shows >> > me /lib/x86_64-linux-gnu/libselinux.so.1 , not the full (pre-pivot-root) >> > path. >> > >> > What versions are you using, and how exactly are you creating and >> > starting the containers? What distros on host and in container? >> > If you add '-l info -o debug.out' to the lxc-start command, what >> > does debug.out then show? >> > >> > -serge >> > > |