How to Install and Uninstall low-memory-monitor Package on openSuSE Tumbleweed
Last updated: December 25,2024
1. Install "low-memory-monitor" package
Learn how to install low-memory-monitor on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
low-memory-monitor
Copied
2. Uninstall "low-memory-monitor" package
In this section, we are going to explain the necessary steps to uninstall low-memory-monitor on openSuSE Tumbleweed:
$
sudo zypper remove
low-memory-monitor
Copied
3. Information about the low-memory-monitor package on openSuSE Tumbleweed
Information for package low-memory-monitor:
-------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : low-memory-monitor
Version : 2.1-3.12
Arch : x86_64
Vendor : openSUSE
Installed Size : 68.5 KiB
Installed : No
Status : not installed
Source package : low-memory-monitor-2.1-3.12.src
Upstream URL : https://gitlab.freedesktop.org/hadess/low-memory-monitor
Summary : Early boot daemon to monitor memory pressure and react to low memory
Description :
The Low Memory Monitor is an early boot daemon that will monitor memory
pressure information coming from the kernel, and, when memory pressure means
that memory isn't as readily available and would cause interactivity problems,
would:
* send D-Bus signals to user-space applications when memory is running low,
* if configured to do so and memory availability worsens, activate the kernel's
OOM killer.
-------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : low-memory-monitor
Version : 2.1-3.12
Arch : x86_64
Vendor : openSUSE
Installed Size : 68.5 KiB
Installed : No
Status : not installed
Source package : low-memory-monitor-2.1-3.12.src
Upstream URL : https://gitlab.freedesktop.org/hadess/low-memory-monitor
Summary : Early boot daemon to monitor memory pressure and react to low memory
Description :
The Low Memory Monitor is an early boot daemon that will monitor memory
pressure information coming from the kernel, and, when memory pressure means
that memory isn't as readily available and would cause interactivity problems,
would:
* send D-Bus signals to user-space applications when memory is running low,
* if configured to do so and memory availability worsens, activate the kernel's
OOM killer.