What does the %CPU field mean in the output of ps and why the sum of %CPU for all process can go above 100%?
Strange how some parts of a program you never use even if you have the used the program for ages.
Did you know Linux PS has test fields? I didn't and I look after it!
The field names are like _left, _left2 or _unlimited and they are statically defined. I found out about them by crashing the new library.
The watch program from the #procps package has a new trick. Someone asked if there was a way to truncate the output instead of line-wrapping.
Watch already detects the width of the screen because it uses ncurses to output the lines so it needs to know where on the screen the next character will go. It was just a matter of hooking into the "run out of width" part of the code and eat the input until we hit an end of line.
So soon if you want to chomp those lines, you can!
Recently pushed a change to fix the -C flag in ps. The command name length was increased to 63 characters from 15 but most non kernel threads can only do 15 characters.
So how can ps match both 15 and 63 characters?
If the process' comm is 15 and the match is 15 or more then match the first 15 characters.
Also keep matching the entire string up to 63 characters.
Are you one of those people with some mad system with lots of CPUs? Having a hard time trying to see them all? Well top is coming out with two new features.
The first is two CPUs per row for wide (about over 160 columns) screens.
The second is to be able to group cpus into, um groups, so you can see pairs of cpu stats aggregated or 4 aggregated etc.
#autopkgtest is very useful facility to check for Debian packages as-installed. It probably has the second-worst documentation in history (the first being sendmail).
If I actually understood it, I'd fix the documentation, but I don't.
Is there anything more confusing than shared library numbering?
There are three numbers: current, revision and age. Depending on what you are doing to the API one or more of those numbers will change. Seems the last #procps relase I did months ago I got it wrong and bumped the age when that can't happen by itself, I think.
Oh and the soname of the library is definitely connected to, but not exactly, those three numbers (I think its C.R.R-A or something like that).
I just realised my intro went when my instance crashed all those months ago.
My day job is a senior #networkengineer working on some very large and strange computer networks.
Procps-ng version 3.3.13 just got released. I have tagged and signed
the last commit and pushed it to gitlab. I will soon start on the
Debian packages and other distributions are free to update as well.
Thankyou to all the contributors!
What's been cooking in procps tonight?
A few new merge requests completed. sysctl will accept huge input; pidof you can specify the separator between PIDs and ps has seconds display for cputime
Next one, possibly tomorrow, will be to adjust pkill so it doesn't kill outside its container by default.
Free Software programmer, network engineer and Debian developer.
100% tomato verified. 🍅✔
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!