true but not relevant as the call is only to extract the cpu count to determine how many threads to safely spawn. So a snapshot of cpuinfo during full speed mode would be best. If the system is running 4 cores and named needs that much horsepower, dynamic data is not a good thing. :)<br>
<br><div class="gmail_quote">On Tue, Apr 1, 2008 at 11:00 PM, Jim Popovitch <<a href="mailto:yahoo@jimpop.com">yahoo@jimpop.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/4/1 Jim Kinney <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>>:<br>
<div class="Ih2E3d">> So only /proc/cpuinfo needs to be in the chroot for bind to find all the<br>
> cpu's. As the data in cpuinfo is static (unless you reboot and change the<br>
> cpu's physically) a copy can be placed in the /var/chroot/ and that should<br>
> suffice.<br>
<br>
</div>er, /proc/cpuinfo is dynamic as some systems show CPU metrics like<br>
speed and temperature. ;-)<br>
<br>
-Jim P.<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III <br>