<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small">Andrea:</div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Permits seem to be correct:<br>
<br>
dr-xr-xr-x 403 root root 0 27 giu 08.47 proc<br></blockquote><div><span class="gmail_default" style="font-size:small">Because GG had to update Arch today to prepare for June 30 builds, he decided to </span><span class="gmail_default" style="font-size:small">test anyway on that Arch. Permissions were the exact same as yours on the /proc/cpuinfo file. <br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
But don't waste your time with this problem of mine. Using Render Farm<br>
is a great alternative.<br></blockquote><div><span class="gmail_default" style="font-size:small">Since he had it booted anyway, </span><span class="gmail_default" style="font-size:small">he logged in as an ordinary user, did a Render, and it used 1100% of a 16 core cpu. So we have no idea what the problem is but you are happy with your workaround. Do you think that the Render Farm usage in the manual needs improvements? I forgot to mention that the referenced section 6.4.1 is enhanced with more details in 6.4.3 so maybe that should be referred to instead of improvements?</span><br>
</div></div></div>