[CRIU] [PATCHv4 0/4] libcriu

Pavel Emelyanov xemul at parallels.com
Wed Sep 4 05:26:28 EDT 2013


On 09/04/2013 01:07 PM, Ruslan Kuprieiev wrote:
> On 09/04/2013 12:54 PM, Pavel Emelyanov wrote:
>> On 09/04/2013 10:01 AM, Ruslan Kuprieiev wrote:
>>
>>>> But, it looks like sending a file descriptor can only easily be done in C
>>>> code, but in e.g. Python or Java this is painful, so we probably would have
>>>> to reconsider the way we send images dir fd to the service (need more
>>>> thinking).
>>>>
>>> Is libcriu in the same address namespace as user program? If so, user
>>> program could pass folder path to libcriu, and, as libcriu has the same
>>> uid\gid\pid, it could open it(just like user program could) and send fd
>>> to criu. So it won't matter, what language user program is using.
>> Java can't use libcriu.so. The intention is to describe the protocol in
>> documentation and make protobuf messages open. Thus in any language, that
>> has protobuf bindings it would be possible to send 'dump-me' request.
>>
>> Thanks,
>> Pavel
>>
> So libcriu.so is only for c programs, and programs in other languages, 
> should use protobuf msg and send it to socket manually? So, maybe, we 
> should reject making libcriu.so, and make cr_service() and documentation 
> to args?

In the 1st version -- it can be enough, yes. But having .so for C and .py for
python would be handy.


More information about the CRIU mailing list