How to Install and Uninstall libmessage-passing-zeromq-perl Package on Ubuntu 21.04 (Hirsute Hippo)

Last updated: May 08,2024

1. Install "libmessage-passing-zeromq-perl" package

Please follow the guidelines below to install libmessage-passing-zeromq-perl on Ubuntu 21.04 (Hirsute Hippo)

$ sudo apt update $ sudo apt install libmessage-passing-zeromq-perl

2. Uninstall "libmessage-passing-zeromq-perl" package

This is a short guide on how to uninstall libmessage-passing-zeromq-perl on Ubuntu 21.04 (Hirsute Hippo):

$ sudo apt remove libmessage-passing-zeromq-perl $ sudo apt autoclean && sudo apt autoremove

3. Information about the libmessage-passing-zeromq-perl package on Ubuntu 21.04 (Hirsute Hippo)

Package: libmessage-passing-zeromq-perl
Architecture: all
Version: 0.010-2
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 98
Depends: libanyevent-perl, libfile-pushd-perl, libmessage-passing-perl, libmoo-perl, libposix-atfork-perl, libsub-name-perl, libtask-weaken-perl, libtry-tiny-perl, libzmq-ffi-perl, libnamespace-clean-perl, libmoox-types-mooselike-perl, perl
Filename: pool/universe/libm/libmessage-passing-zeromq-perl/libmessage-passing-zeromq-perl_0.010-2_all.deb
Size: 34982
MD5sum: f9bc845bed1f10302454e5ea6849f8b5
SHA1: 116169df29c5f2471570be2e6d31c93f908d4b61
SHA256: fad86aaddea7dba45436f071015189f9b3fd1a540d0afa6665f343746f666dab
SHA512: b791eaee7a9738459d9b9900c7bc0387e1a5473e56e038c181c0f9df0baffb13bb108009150349a0fbe48d14c9dbaab1252a5cdb64788d2c9112142edef17a85
Homepage: http://search.cpan.org/dist/Message-Passing-ZeroMQ/
Description-en: input and output messages to ZeroMQ
Message::Passing::ZeroMQ is a ZeroMQ transport for Message::Passing.
.
Designed for use as a log transport and aggregation mechanism for perl
applications, allowing you to aggregate structured and non-structured
log messages across the network in a non-blocking manner.
.
Clients (i.e. users of the Message::Passing::Output::ZeroMQ class)
connect to a server (i.e. a user of the Message::Passing::Input::ZeroMQ
class) via ZeroMQ's pub/sub sockets. These are setup to be lossy and
non-blocking, meaning that if the log-receiver process is down or slow,
then the application will queue a small (and configurable) amount of
logs on its side, and after that log messages will be dropped.
.
Whilst throwing away log messages isn't a good thing to do, or
something that you want to happen regularly, in many (especially web
application) contexts, network logging being a single point of failure
is not acceptable from a reliability and graceful degradation
standpoint.
.
The application grinding to a halt as a non-essential centralised
resource is unavailable (e.g. the log aggregation server) is
significantly less acceptable than the loss of non-essential logging
data.
Description-md5: 6c3d6a8b97c6321fe8a6d5c74e417e68