[ale] chroot and /proc?

[Jim Kinney]

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. :)

On Tue, Apr 1, 2008 at 11:00 PM, Jim Popovitch <yahoo at jimpop.com> wrote:

> 2008/4/1 Jim Kinney <jim.kinney at gmail.com>:
> > So only /proc/cpuinfo needs to be in the chroot for bind to find all the
> > cpu's. As the data in cpuinfo is static (unless you reboot and change
> the
> > cpu's physically) a copy can be placed in the /var/chroot/ and that
> should
> > suffice.
>
> er, /proc/cpuinfo is dynamic as some systems show CPU metrics like
> speed and temperature. ;-)
>
> -Jim P.
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>



-- 
-- 
James P. Kinney III
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20080401/85165096/attachment-0001.html