ok, so you check the boinc scheduler request (or event log) rather than look at /proc/cpuinfo ? I guess since I'd be doing it in the benchmarks I'll use cpuinfo as there may not have been a scheduler request by then ie I may be the first thing called after a new download etc.
we probably need a more persistent cpu/fpu reporting though for apps, maybe a var in boinc_api, i.e. do we want an app always parsing /proc/cpuinfo or client_state.xml all the time etc? _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
