[CRIU] [PATCH 0/3] introduce selective dump

[Ruslan Kuprieiev]

It can be notified in two ways(but not limited to these):
1) our usual RPC way of putting a resp packet on restore into a criu 
service socket
2) --external unix[ino]:stub[string] for those that are not connected 
directly to criu

We currently use the 2) because of the reasons I described in respective 
patch description.

Sure, if there is more generic way I would be happy to adopt it.

Sorry for not being active enough on these patches, I hope to get back 
to them in a week
or so.


On 03/24/2017 02:26 AM, Andrei Vagin wrote:
> On Mon, Feb 27, 2017 at 01:39:50PM +0200, Ruslan Kuprieiev wrote:
>> This patch set introduces --pid option back, which now allows one to
>> select process within specified process tree that needs to be checkpointed.
> How does an application will know that it has to create new workers
> after restore? Do you notify it somehow?
>
> Maybe we can find more genreic way how to say for which processes we
> don't need children?
>
>> Ruslan Kuprieiev (3):
>>    crtools: resurrect --pid option for dump
>>    rpc: add target_pid option
>>    service: fix typo/bug
>>
>>   criu/cr-service.c         |  5 ++++-
>>   criu/crtools.c            |  8 +++++---
>>   criu/include/cr_options.h |  1 +
>>   criu/seize.c              | 11 +++++++----
>>   images/rpc.proto          |  1 +
>>   lib/c/criu.c              | 11 +++++++++++
>>   lib/c/criu.h              |  2 ++
>>   7 files changed, 31 insertions(+), 8 deletions(-)
>>
>> -- 
>> 2.9.3
>>
>> _______________________________________________
>> CRIU mailing list
>> CRIU at openvz.org
>> https://lists.openvz.org/mailman/listinfo/criu
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu