How to Install and Uninstall libschedule-ratelimiter-perl Package on Ubuntu 21.10 (Impish Indri)

Last updated: November 26,2024

1. Install "libschedule-ratelimiter-perl" package

Here is a brief guide to show you how to install libschedule-ratelimiter-perl on Ubuntu 21.10 (Impish Indri)

$ sudo apt update $ sudo apt install libschedule-ratelimiter-perl

2. Uninstall "libschedule-ratelimiter-perl" package

In this section, we are going to explain the necessary steps to uninstall libschedule-ratelimiter-perl on Ubuntu 21.10 (Impish Indri):

$ sudo apt remove libschedule-ratelimiter-perl $ sudo apt autoclean && sudo apt autoremove

3. Information about the libschedule-ratelimiter-perl package on Ubuntu 21.10 (Impish Indri)

Package: libschedule-ratelimiter-perl
Architecture: all
Version: 0.01-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: 26
Depends: perl
Filename: pool/universe/libs/libschedule-ratelimiter-perl/libschedule-ratelimiter-perl_0.01-2_all.deb
Size: 9436
MD5sum: af8b9d2ae6aea59d24d74d5047b525a2
SHA1: 21efa12b46418c636ca259dee0db20bdd69e264d
SHA256: ad49c49809c704411d42ee4bf57940a2f5939129ff56a3818dc74cff8b2ed9ba
SHA512: 6ba521086beec4ef750dcd9e677300e23448e38407f7b0b0e5633c6c330eb3d6e7d5795d16c4981b6d02032ea119a8aa290a3ab8b619a09195fb307454cbc1ff
Homepage: https://metacpan.org/release/Schedule-RateLimiter
Description-en: Perl library to prevent events from happening too quickly
Schedule::RateLimiter provides a way to voluntarily restrict how many times a
given action may take place within a specified time frame. Such a tool may be
useful if you have written something which periodically polls some public
resource and want to ensure that you do not overburden that resource with too
many requests.
.
Initially, one might think that solving this problem would be as simple as
sleeping for the number of seconds divided by the number of iterations in
between each event. However, that would only be correct if the event took no
time at all.
.
If you know exactly how much time each event is going to take then you could
build an even more complicated one-liner such as this:
.
sleep( (seconds / iterations) - single_event_time )
Description-md5: 8b6c6a0ff5363c57f63a662f58a1b5ce