summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGiampaolo Rodola <g.rodola@gmail.com>2022-01-07 21:33:18 +0100
committerGiampaolo Rodola <g.rodola@gmail.com>2022-01-07 21:33:18 +0100
commit4e1cb960dc26b74a200cc5278066c1ffcc6ad71c (patch)
tree4f532931ea0f53bfe34cfd9fa33dd0b1caf2aad5
parent5364d4c287f1968d6bb11e5db08b5411118abfe4 (diff)
downloadpsutil-4e1cb960dc26b74a200cc5278066c1ffcc6ad71c.tar.gz
update HISTORY
Signed-off-by: Giampaolo Rodola <g.rodola@gmail.com>
-rw-r--r--HISTORY.rst3
-rw-r--r--psutil/_pslinux.py1
2 files changed, 3 insertions, 1 deletions
diff --git a/HISTORY.rst b/HISTORY.rst
index cef15236..480d59f5 100644
--- a/HISTORY.rst
+++ b/HISTORY.rst
@@ -9,6 +9,9 @@
manually and passed through ``str``.
- 2049_, [Linux]: `cpu_freq`_ erroneously returns ``curr`` value in GHz while
``min`` and ``max`` are in MHz.
+- 1915_, [Linux]: ``virtual_memory``_ may return ```0`` as ``available`` memory
+ on certain distros, in which case we calculate an appromixation which matches
+ ``free`` CLI utility.
5.9.0
=====
diff --git a/psutil/_pslinux.py b/psutil/_pslinux.py
index 9cb799ed..20dd85cb 100644
--- a/psutil/_pslinux.py
+++ b/psutil/_pslinux.py
@@ -379,7 +379,6 @@ def calculate_avail_vmem(mems):
It is still way more realistic than doing (free + cached) though.
See:
* https://gitlab.com/procps-ng/procps/issues/42
- * https://gitlab.com/procps-ng/procps/-/issues/42
* https://github.com/famzah/linux-memavailable-procfs/issues/2
"""
# Note about "fallback" value. According to: