[CRIU] Towards an in-process libcriu

[Ruslan Kuprieiev]

So, that lib would do smth like fork+exec criu? And criu process would 
be in the
tree that you want to dump, right?

On 16.07.2014 21:41, Tycho Andersen wrote:
> Hi Ruslan,
>
> On Wed, Jul 16, 2014 at 09:10:36PM +0300, Ruslan Kuprieiev wrote:
>> Hi Tycho,
>>
>> could you describe what do you want to do and why libcriu and RPC
>> don't match
>> your needs?
> I'm working on integrating criu directly into lxc, so there can be
> commands like lxc-checkpoint and lxc-restore. If I understand things
> correctly, we'll either have to run a criu daemon all the time, or
> spawn one when they run lxc-{checkpoint,restore}, do the checkpoint or
> restore, and then kill it off. It seems much cleaner to me just to
> have a set of library functions that we could do this with in process.
>
> I'm not necessarily opposed to the idea of using the RPC, I just
> figured it probably wouldn't be that hard to get at least a tiny
> libcriu going that would do what I needed.
>
> Tycho
>
>> Thanks,
>> Ruslan
>>
>> On 16.07.2014 19:37, Tycho Andersen wrote:
>>> Hi all,
>>>
>>> I'm interested in making an in-process version of libcriu, as opposed
>>> to the RPC version that currently exists today. I can tack it on to
>>> the existing libcriu and include the necessary symbols, or I could
>>> start out fresh. Which option is preferable? Also, if I start fresh,
>>> what should I call such a thing?
>>>
>>> Thanks,
>>>
>>> Tycho
>>> _______________________________________________
>>> CRIU mailing list
>>> CRIU at openvz.org
>>> https://lists.openvz.org/mailman/listinfo/criu