On Mon, Jul 23, 2018 at 10:07:03AM +0200, Marcus MERIGHI wrote: > I've noticed that systat(1), in the CPU bar graph, shows "@"s, which > aren't explained in systat(1). I went looking and found:
This commit is more relevant as I fixed the output afterwards. src/usr.bin/systat/vmstat.c ---------------------------- revision 1.85 date: 2018/05/19 13:24:10; author: bluhm; state: Exp; lines: +6 -4; commitid: 4ynbHJn9ppGCJ82S; Do not ignore nice time in systat(1). The sum would not be 100%, a busy machine would look idle. As %Nic does not fit in the columns, add it to %Usr. Introduce @ for spinning time to keep the characters people are used to. Put %Spn between %Int and %Sys like in top. OK visa@ mpi@ ---------------------------- Unfortunately I forgot the man page. top(1) is also incomplete. ok? bluhm Index: usr.bin/systat/systat.1 =================================================================== RCS file: /data/mirror/openbsd/cvs/src/usr.bin/systat/systat.1,v retrieving revision 1.109 diff -u -p -r1.109 systat.1 --- usr.bin/systat/systat.1 8 Jul 2018 13:23:57 -0000 1.109 +++ usr.bin/systat/systat.1 23 Jul 2018 09:27:45 -0000 @@ -460,12 +460,12 @@ Below the queue length listing is a nume a bar graph showing the amount of interrupt (shown as .Ql | ) , +spinning (shown as +.Ql @ ) , system (shown as .Ql = ) , -user (shown as +user plus nice (shown as .Ql > ) , -nice (shown as -.Ql - ) , and idle time (shown as .Ql \ \& ) . .Pp Index: usr.bin/top/top.1 =================================================================== RCS file: /data/mirror/openbsd/cvs/src/usr.bin/top/top.1,v retrieving revision 1.68 diff -u -p -r1.68 top.1 --- usr.bin/top/top.1 8 Sep 2016 16:47:47 -0000 1.68 +++ usr.bin/top/top.1 23 Jul 2018 09:25:32 -0000 @@ -388,7 +388,7 @@ the number of existing processes, the number of processes in each state (starting, running, idle, stopped, zombie, dead, and on processor), and a percentage of time spent in each of the processor states -(user, nice, system, interrupt, and idle). +(user, nice, system, spinning, interrupt, and idle). It also includes information about physical and virtual memory allocation. The load average numbers give the number of jobs in the run queue averaged over 1, 5, and 15 minutes.
