On 16/05/2020 01.25, Dave Howorth wrote:
On Fri, 15 May 2020 21:52:01 +0200 (CEST) "Carlos E. R." <> wrote:
On Friday, 2020-05-15 at 07:08 -0400, Anton Aylward wrote:
On 11/05/2020 06:11, Carlos E. R. wrote:
...
I suggest that 'vmstat -SM -a 15' in an xterm will tell you more about what's going on than 'top'.
I tried, I find it cryptic.
Telcontar:~ # vmstat -SM -a 15 procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free inact active si so bi bo in cs us sy id wa st 1 0 1330 17369 2280 10992 0 0 332 146 51 38 6 1 92 0 0 0 0 1330 17477 2280 10882 0 0 0 16 3454 5955 2 0 97 0 0 1 0 1330 17461 2280 10901 0 0 0 27 3250 5629 2 0 97 0 0
What is each column?
man vmstat?
I'll bite. "man vmstat" then search for "columns" produces nothing. I'm not the one that wants to use vmstat, so it is possible that Anton already knows and can tell me faster than me finding out :-)
After a while, the header disapears, so I don't even have that minimal information. The header should not flow out.
That depends on what assumptions it makes about the capabilities of the device its output is rendered by. You seek to prevent it rendering on basic devices? You can always write a filter to apply afterwards.
You could have said that it prints the headers again every while. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)