<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Tycho,<br>
<br>
The only difference I see between existing libcriu and the one you
want to make, is<br>
running criu service. Criu service was designed to be used as
system service, so<br>
you could just make it run on start of your system using <a
href="http://criu.org/RPC#systemd">provided</a> systemd<br>
configs. Then, using libcriu is just as simple as #include criu.h
and dump().<br>
<br>
Indeed, creating libcriu in the form you suggested seems to me
like a lot of work <br>
and after that we will come up with libcriu with reduced
functionality, as it wouldn't<br>
be able to run as non-root, perform a self-dump etc.<br>
<br>
But that's just my personal opinion. Maybe others would say smth
else.<br>
<br>
Thanks,<br>
Ruslan<br>
<br>
On 17.07.2014 00:50, Tycho Andersen wrote:<br>
</div>
<blockquote cite="mid:20140716215021.GI21743@smitten" type="cite">
<pre wrap="">Hi Ruslan,
On Wed, Jul 16, 2014 at 11:38:29PM +0300, Ruslan Kuprieiev wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Oh! I see. But there is another problem. I believe, criu doesn't
free all resources
after it is done its work.
</pre>
</blockquote>
<pre wrap="">
I understand that, but I suppose those are mostly bugs in criu that
will be fixed. Supposing that I'm ok with the caveats (potential
resource leaks, can't dump the tree with me in it, etc.), it would be
nice not to have to fork() and set up a socket and all that, but
rather just #include criu.h and dump(other_pid). If it is a lot of work
or doesn't fit with the project, I'm happy to go with the fork model,
but I think it shouldn't be that hard to get something minimal going.
I'm just unsure of where the best place for it to live is.
Tycho
</pre>
</blockquote>
<br>
</body>
</html>