<div dir="ltr">Oh, so probably this is because I ran the test from emacs shell. So the socket was opened in the emacs shell parent process and that's why criu test picked it up?</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Nov 26, 2013 at 11:08 AM, Cyrill Gorcunov <span dir="ltr"><<a href="mailto:gorcunov@gmail.com" target="_blank">gorcunov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Nov 26, 2013 at 10:57:04AM -0500, Neal Becker wrote:<br>
> Sure, it's used by emacs. But what's criu doing poking around there?<br>
<br>
</div>Such socket (which is collected during pre-dump phase) will be skipped when<br>
the real dump process initiated. As to "what's criu doing" -- we collect<br>
sockets information provided by a kernel thus when we dump process we can<br>
be sure the socket we're dumping (especially unix ones) can be restored<br>
later. Could you please attach the complete dump.log, not just a snippet<br>
of it?<br>
</blockquote></div><br></div>