How to Install and Uninstall chronic Package on openSuSE Tumbleweed
Last updated: November 08,2024
1. Install "chronic" package
This guide covers the steps necessary to install chronic on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
chronic
Copied
2. Uninstall "chronic" package
Please follow the instructions below to uninstall chronic on openSuSE Tumbleweed:
$
sudo zypper remove
chronic
Copied
3. Information about the chronic package on openSuSE Tumbleweed
Information for package chronic:
--------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : chronic
Version : 0.68-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 22.6 KiB
Installed : No
Status : not installed
Source package : moreutils-0.68-1.2.src
Upstream URL : https://joeyh.name/code/moreutils/
Summary : Runs a command quietly unless it fails
Description :
chronic runs a command, and arranges for its standard out and standard
error to only be displayed if the command fails (exits nonzero or crashes).
If the command succeeds, any extraneous output will be hidden.
A common use for chronic is for running a cron job. Rather than
trying to keep the command quiet, and having to deal with mails containing
accidental output when it succeeds, and not verbose enough output when it
fails, you can just run it verbosely always, and use chronic to hide
the successful output.
--------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : chronic
Version : 0.68-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 22.6 KiB
Installed : No
Status : not installed
Source package : moreutils-0.68-1.2.src
Upstream URL : https://joeyh.name/code/moreutils/
Summary : Runs a command quietly unless it fails
Description :
chronic runs a command, and arranges for its standard out and standard
error to only be displayed if the command fails (exits nonzero or crashes).
If the command succeeds, any extraneous output will be hidden.
A common use for chronic is for running a cron job. Rather than
trying to keep the command quiet, and having to deal with mails containing
accidental output when it succeeds, and not verbose enough output when it
fails, you can just run it verbosely always, and use chronic to hide
the successful output.