Re: sysctlbyname( "hw.availcpu" ) fails
Re: sysctlbyname( "hw.availcpu" ) fails
- Subject: Re: sysctlbyname( "hw.availcpu" ) fails
- From: Steve Checkoway <email@hidden>
- Date: Fri, 29 Jun 2007 01:33:31 -0700
On Jun 29, 2007, at 1:17 AM, Michael Smith wrote:
On Jun 28, 2007, at 12:04 PM, email@hidden
wrote:
Thank you both for the information. As I mentioned in my first email,
I'm actually doing anything with this information, I just like to see
what people are running when I get crash reports.
I assume you mean "not actually doing anything"?
Heh, yes. I am _not_ actually doing anything with it.
If you're really looking for a broad swath of information, I would
encourage you to consider invoking system_profiler(8), and
ioreg(8). The combination of these two will tell you far more than
you ever wanted to know about your customers' systems.
Oh yes, that would be far more than I'd ever want to know and possibly
more than they'd care to send me. The model of the processor, the
number of them, their speed, the version of the OS and the amount of
RAM they have installed is about all I was really looking for. Plus,
$ time system_profiler > /dev/null
real 0m4.025s
user 0m0.753s
sys 0m0.639s
That's more time than I'd care to take on start up. I appreciate the
suggestions though. I've been using Gestalt and figured I should maybe
move to some newer interface.
--
Steve Checkoway
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden