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.
Got a real puzzle around how #Linux handles NFS mounts. From the same server they have the same device ID. This means things like fuser don't work.
Files that are opened by a process are found in /proc/PID/fd and fuser stat()s them to find the device ID, then it scans the mounts to match so you can do things like "who has files open under /mydir"?
For NFS this just does not work because all mounts from the same server will state they have files open.
The #debian project is planning on holding a mini DebConf online.
This will be "4 days of Debianites working together to improve Debian" and will be totally online like all the cool kids are doing.
It will be 28-31st May 2020, more details at https://wiki.debian.org/DebianEvents/internet/2020/MiniDebConfOnline
The venerable kill and signal action is used to send signals across processes, but you can also send small amounts of data across in the signal.
I just found out someone still maintains one of the first free software programs I wrote so many years ago. Checked the changelog and it was 25 July 1995! A 24 -year old program still in use.
There has been a bit of a clean up and all my comment out debug code removed (good!) but its basically the same.
Fortunately the Linux kernel driver I wrote has long gone 😱
The issue is, people are used to programs truncating to 15 characters, so things stopped matching.
I just uploaded a fix so if the process name is exactly 15 characters long and the given option is longer, it will match at 15 characters too
Dumb things you can do with Emoji and prctl
At least now my #Linux lockups seem solved. For some reason kernel 4.14 would lock the system up hard or kernel if I used update-rc.d in multi-user mode.
4.13 or booting into single-user mode didn't have this problem.
After a full update it seems to have gone away.
Is Procps insecure? No, but your kernel and filesystem hard links may be and the bug is about enabling the fs.protected_hardlinks parameter
A lot of kernels have this on by default but this is in case yours does not and Debian Procps will set it to on. This change won't be in the upstream Procps.
A little while ago the Linux kernel developers snuck in the I state, for those idle kernel threads that wait for something to happen but not like a process (so no need to increase loadavg).
ps and top just copy the state across but didn't document it; until today.
I never knew about the idle state for processes or why you would need it, but now I do. Bug reports can be educational!
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!