How to Install and Uninstall libmessage-passing-zeromq-perl Package on Ubuntu 16.04 LTS (Xenial Xerus)
Last updated: December 25,2024
1. Install "libmessage-passing-zeromq-perl" package
Please follow the guidelines below to install libmessage-passing-zeromq-perl on Ubuntu 16.04 LTS (Xenial Xerus)
$
sudo apt update
Copied
$
sudo apt install
libmessage-passing-zeromq-perl
Copied
2. Uninstall "libmessage-passing-zeromq-perl" package
Please follow the guidelines below to uninstall libmessage-passing-zeromq-perl on Ubuntu 16.04 LTS (Xenial Xerus):
$
sudo apt remove
libmessage-passing-zeromq-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libmessage-passing-zeromq-perl package on Ubuntu 16.04 LTS (Xenial Xerus)
Package: libmessage-passing-zeromq-perl
Priority: optional
Section: universe/perl
Installed-Size: 137
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Architecture: all
Version: 0.007-1
Depends: libanyevent-perl, libmessage-passing-perl, libmoo-perl, libposix-atfork-perl, libsub-name-perl, libtask-weaken-perl, libtry-tiny-perl, libzeromq-perl, libnamespace-clean-perl, perl
Filename: pool/universe/libm/libmessage-passing-zeromq-perl/libmessage-passing-zeromq-perl_0.007-1_all.deb
Size: 39278
MD5sum: e5de67e1e24b0c808f97eba3fe417a01
SHA1: cb3d1635528de501c895665fc2e4e411cf1fbe39
SHA256: 2c1e376ad1ee9aaf7838372bf3198312db4311413df609ee26c17cd4401738b4
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
Homepage: http://search.cpan.org/dist/Message-Passing-ZeroMQ/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu
Priority: optional
Section: universe/perl
Installed-Size: 137
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Architecture: all
Version: 0.007-1
Depends: libanyevent-perl, libmessage-passing-perl, libmoo-perl, libposix-atfork-perl, libsub-name-perl, libtask-weaken-perl, libtry-tiny-perl, libzeromq-perl, libnamespace-clean-perl, perl
Filename: pool/universe/libm/libmessage-passing-zeromq-perl/libmessage-passing-zeromq-perl_0.007-1_all.deb
Size: 39278
MD5sum: e5de67e1e24b0c808f97eba3fe417a01
SHA1: cb3d1635528de501c895665fc2e4e411cf1fbe39
SHA256: 2c1e376ad1ee9aaf7838372bf3198312db4311413df609ee26c17cd4401738b4
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
Homepage: http://search.cpan.org/dist/Message-Passing-ZeroMQ/
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu