diff options
| author | Thorsten Töpper <atsutane@freethoughts.de> | 2025-08-24 22:43:37 +0200 |
|---|---|---|
| committer | Thorsten Töpper <atsutane@freethoughts.de> | 2025-08-24 22:43:37 +0200 |
| commit | e5ad2a19e67d9cb50d4bd961e86a904936a6c689 (patch) | |
| tree | 68fba3f9e54efb1f2654839914fac61e5387efc9 /niflheim | |
| parent | 3f6df1cf100e0c078b988a56e6c9da9efa36c83b (diff) | |
| download | dotfiles-e5ad2a19e67d9cb50d4bd961e86a904936a6c689.tar.gz dotfiles-e5ad2a19e67d9cb50d4bd961e86a904936a6c689.tar.bz2 | |
niflheim/i3status: Show memory available if >90% are used.
Until today never noticed this minor error in my configuration.
Note for those not familiar with the difference:
On Linux free memory is completely unused memory, a total waste of this
ressource. Important is the memory categorized as available, this covers
caches/buffers meaning data which isn't required to be kept in-memory
but there for performance and other improvements. Free memory is part of
available memory so if there are 300MiB free, but 25GiB available you
won't have a problem starting the greedy web-browser due to a memory
shortage.
Details can be found in /proc/meminfo and related Linux kernel
documentation. In the latter probably also somewhere the criteria by
which is chosen what to remove from the cache for a process allocation.
Diffstat (limited to 'niflheim')
| -rw-r--r-- | niflheim/config/i3status/config | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/niflheim/config/i3status/config b/niflheim/config/i3status/config index ed8554c..55446f4 100644 --- a/niflheim/config/i3status/config +++ b/niflheim/config/i3status/config @@ -51,7 +51,7 @@ cpu_temperature 0 { memory { format = "RAM: %used used" threshold_degraded = "10%" - format_degraded = "RAM: %free free" + format_degraded = "RAM: %available available" } disk "/" { |