brownfoki.blogg.se - Top cpu processes geektool

TOP CPU PROCESSES GEEKTOOL FREE

The while loop then tames the log's growth by emptying it once a minute. #!/usr/bin/env pythonimport os, timeos.system("top -l0 -n45 -s3 -S > /var/tmp/top.log &")while True: open("/var/tmp/top.log","w").close() time.sleep(60)Here the os.system line spawns one top process, which forever ( -l0) keeps sending 45 lines, every three seconds, to our top.log. Be sure to make it executable by running chmod a+x on it, so it will execute.

Put the following script, top.py, in ~/Library/Application Support/GeekTool Scripts.

Actually, our script will run only once, but for some reason GeekTool gets far more CPU-intensive if the Refresh field is empty or zero.

Make another new entry of type Shell, with Command: top.py, Size: 0 by 0, Refresh: 10.

This will make GeekTool always display the last 50 lines of this file - internally it runs tail -n50 -F on it.

In the GeekTool Preference Pane, make a new entry top.log of type File, with Path set to /var/tmp/top.log.

In this hint, I describe a different ( k = 0) workaround which appears to solve the problem, i.e. In short, watching top this way perturbs it more than we'd like.

Either way, relaunching top every few seconds soon causes pid's to roll over 30000, so that recent processes must be hunted down the list rather than conveniently appearing on top.

With k > 1, they become skewed by an overestimated CPU usage for top itself.Taking k = 1, the CPU usage line and column stop making sense.Unfortunately it doesn't support self-updating commands like top, and the official workaround (break the loop with top -l k and set Refresh to keep restarting it) is rather Heisenbuggy:

TOP CPU PROCESSES GEEKTOOL FREE

The great and free GeekTool ( PowerPC | Intel) can write the contents of any file, and the output of any shell command, right onto the desktop.