On Fri, Mar 15, 2002 at 10:27:22AM -0800, Terry Lambert wrote: > Josh Paetzel wrote: > > This is a perfect example of, "Just because you can do something, > > doesn't mean you should." > > > > I wouldn't see anything wrong with grabbing the clock frequency of the > > first cpu in the system and noting in the man page that if you have > > multiple cpus and you aren't running them at the same frequency, then > > the reported value is applicable only to the first cpu. > > > > This would save a ton of time in implementing Jordan's ideas, at the > > cost of not being able to deal correctlywith a situation that > > (hopefully) isn't too common in the field. The other less tangible > > disadvantage to my suggestion is that it takes us one step further in our > > single-cpu-centric userland, ala top, uptime, and so forth only > > displaying stats for "one" cpu. > > Incorrect information is always worse than no information. > > -- Terry
Yeah, you're right. Six hours of contemplation and I've changed my tune. If it's going to be done, should be done right. Josh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message