Faster IT

You can get the same info from `/proc/sys/fs/file-nr` on a Linux system (#990). BSD has `sysctl kern.maxfiles` and `sysctl kern.openfiles`. Why not implement it to work outside PCP as well?

> > You can get the same info from `/proc/sys/fs/file-nr` on a Linux system (#990). BSD has `sysctl kern.maxfiles` and `sysctl kern.openfiles`. Why not implement it to work outside PCP...

Needs a bit of discussion on 4 letters vs ugly "Loa". Comments welcome :-)

```bash ./configure --enable-static --disable-unicode --disable-hwloc --disable-setuid --disable-sensors --disable-capabilities --disable-openvz --disable-vserver --disable-ancient-vserver --disable-delayacct --disable-linux-affinity make -j $(nproc) ./htop ``` works here on Ubuntu 20.04.1 LTS, also AMD64 aka cannot reproduce

In the default color profile, we have: ~~~ [PROCESS_THREAD] = ColorPair(Green, Black), [PROCESS_THREAD_BASENAME] = A_BOLD | ColorPair(Green, Black), ~~~ Showing custom thread names, which you have enabled in Setup (F2)...

@BenBE Custom thread names is your turf...

~~~ diff --git a/CRT.c b/CRT.c index 868f2377..4391f7c0 100644 --- a/CRT.c +++ b/CRT.c @@ -156,7 +156,7 @@ static int CRT_colorSchemes[LAST_COLORSCHEME][LAST_COLORELEMENT] = { [PROCESS_THREAD] = ColorPair(Green, Black), [PROCESS_THREAD_BASENAME] = A_BOLD | ColorPair(Green,...

> > @BenBE Custom thread names is your turf... > > Bold (light) has not been used there, as bold is a marker for the executable basename. Aah, that makes...

Now you get greedy, @eworm-de :-)

> Aah, that makes sense. Shall we move the basename to bold cyan or so to make it still differentiate? The bold blue is much more readable than the plain...