[CRIU] Network unlock issue when checkpointing with -R

[Frederico Araujo]

Thanks for the answers!

Regarding removing -R, I believe that, from the user's perspective, it
would be nice to keep it as option.
Why couldn't we just have CRIU perform a normal checkpoint and then, when
-R is passed, it does the restore as post-dump step? No need to change
anything on the checkpoint process, right?

I might be missing something, but if the problem is only related to the
network lock/unlock, I believe this would do.

Thanks,
Fred


On Wed, Oct 30, 2013 at 12:05 PM, Cyrill Gorcunov <gorcunov at gmail.com>wrote:

> On Wed, Oct 30, 2013 at 08:48:29PM +0400, Andrey Wagin wrote:
> >
> > $ criu dump --action-script post-dump.sh ....
> > $ [  $? -eq 32 ] && echo PASS || echo FAIL
> >
> > >
> > > When you mentioned that -R doesn't work, is there other issues apart
> from
> > > the issue related to established connections unlocking on the source
> host?
> >
> > Yes. I can't remember why we decided to not fix the -R option. Pavel
> > or Cyrill, do you know a reason?
>
> Hmm, I must admit I don't remember either. Pavel?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20131030/5e316190/attachment.html>