How to Install and Uninstall monitoring-plugins-by_ssh Package on openSuSE Tumbleweed
Last updated: December 25,2024
1. Install "monitoring-plugins-by_ssh" package
Please follow the guidance below to install monitoring-plugins-by_ssh on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
monitoring-plugins-by_ssh
Copied
2. Uninstall "monitoring-plugins-by_ssh" package
Please follow the guidance below to uninstall monitoring-plugins-by_ssh on openSuSE Tumbleweed:
$
sudo zypper remove
monitoring-plugins-by_ssh
Copied
3. Information about the monitoring-plugins-by_ssh package on openSuSE Tumbleweed
Information for package monitoring-plugins-by_ssh:
--------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : monitoring-plugins-by_ssh
Version : 2.3.5-2.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 35.1 KiB
Installed : No
Status : not installed
Source package : monitoring-plugins-2.3.5-2.1.src
Upstream URL : http://monitoring-plugins.org/
Summary : Execute checks via SSH
Description :
This plugin uses SSH to execute commands on a remote host.
The most common mode of use is to refer to a local identity file with
the '-i' option. In this mode, the identity pair should have a null
passphrase and the public key should be listed in the authorized_keys
file of the remote host. Usually the key will be restricted to running
only one command on the remote server. If the remote SSH server tracks
invocation arguments, the one remote program may be an agent that can
execute additional commands as proxy.
--------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : monitoring-plugins-by_ssh
Version : 2.3.5-2.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 35.1 KiB
Installed : No
Status : not installed
Source package : monitoring-plugins-2.3.5-2.1.src
Upstream URL : http://monitoring-plugins.org/
Summary : Execute checks via SSH
Description :
This plugin uses SSH to execute commands on a remote host.
The most common mode of use is to refer to a local identity file with
the '-i' option. In this mode, the identity pair should have a null
passphrase and the public key should be listed in the authorized_keys
file of the remote host. Usually the key will be restricted to running
only one command on the remote server. If the remote SSH server tracks
invocation arguments, the one remote program may be an agent that can
execute additional commands as proxy.