<div dir="ltr">Thanks a lot! Just tested. Working like a charm =)<div><br></div><div>Best regards, </div><div>Fred</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 11, 2013 at 8:12 AM, Pavel Emelyanov <span dir="ltr"><<a href="mailto:xemul@parallels.com" target="_blank">xemul@parallels.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 10/11/2013 04:53 PM, Frederico Araujo wrote:<br>
> Answering your questions:<br>
><br>
> 1. Yes, I'm running criu inside the container to dump an application using sockets.<br>
> The container in question, was created using the lxc ubuntu template.<br>
><br>
> 2. Yes, I have both files on my host OS and I tested sysctl on it. It works fine.<br>
> The problem is on the container environment, which does not have the files (it has tcp_mem, but not tcp_rmem and tcp_wmem).<br>
><br>
> Do you know why these files are not mounted on the container?<br>
<br>
</div>It was decided during net-namespaces development, that container wouldn't have to<br>
know these data.<br>
<div class="im"><br>
> I tried to bind only the ipv4 directory from the host using the containers fstab, but didn't<br>
> work; I couldn't see the files in there.<br>
<br>
</div>It's not about mounting, it's about how net namespaces work in the kernel.<br>
I'll tune criu so it will work w/o these sys-controls at hands.<br>
<br>
> Thanks.<br>
</blockquote></div><br></div>