Talk:Linux CPU utilization: Difference between revisions

From Rosetta Code
Content added Content deleted
(Created page with "I think this task is pretty much ready to go... but as its the first task I've added to Rosetta Code, I'd like to get someone to review it first :) --~~~~")
 
(→‎OS specific task: new section)
Line 1: Line 1:
I think this task is pretty much ready to go... but as its the first task I've added to Rosetta Code, I'd like to get someone to review it first :)
I think this task is pretty much ready to go... but as its the first task I've added to Rosetta Code, I'd like to get someone to review it first :)
--[[User:Paul|Paul]] ([[User talk:Paul|talk]]) 09:49, 27 May 2015 (UTC)
--[[User:Paul|Paul]] ([[User talk:Paul|talk]]) 09:49, 27 May 2015 (UTC)

== OS specific task ==

I don't think OS specific tasks are a good idea.
Does this really need to be OS specific?

For starters, <tt>/proc</tt> is '''not''' unique to Linux,
although other OSes may provide other/better ways to get similar information
(e.g. <code>getloadavg(3)</code>).

Some programming languages may provide OS agnostic routines/libraries to get similar information
(which would be superior to grepping around in <tt>/proc/stat</tt> IMO).

Revision as of 13:35, 27 May 2015

I think this task is pretty much ready to go... but as its the first task I've added to Rosetta Code, I'd like to get someone to review it first :) --Paul (talk) 09:49, 27 May 2015 (UTC)

OS specific task

I don't think OS specific tasks are a good idea. Does this really need to be OS specific?

For starters, /proc is not unique to Linux, although other OSes may provide other/better ways to get similar information (e.g. getloadavg(3)).

Some programming languages may provide OS agnostic routines/libraries to get similar information (which would be superior to grepping around in /proc/stat IMO).