How to Install and Uninstall libobject-forkaware-perl Package on Ubuntu 21.04 (Hirsute Hippo)
Last updated: December 23,2024
1. Install "libobject-forkaware-perl" package
Please follow the steps below to install libobject-forkaware-perl on Ubuntu 21.04 (Hirsute Hippo)
$
sudo apt update
Copied
$
sudo apt install
libobject-forkaware-perl
Copied
2. Uninstall "libobject-forkaware-perl" package
Please follow the steps below to uninstall libobject-forkaware-perl on Ubuntu 21.04 (Hirsute Hippo):
$
sudo apt remove
libobject-forkaware-perl
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the libobject-forkaware-perl package on Ubuntu 21.04 (Hirsute Hippo)
Package: libobject-forkaware-perl
Architecture: all
Version: 0.005-1.1
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 30
Depends: perl:any
Filename: pool/universe/libo/libobject-forkaware-perl/libobject-forkaware-perl_0.005-1.1_all.deb
Size: 10252
MD5sum: 025f1089434800e0394cd036c0a9f0d3
SHA1: b468f61112007c2e5c6d51f62304ee318c214797
SHA256: f4caa98a6953d17b907cd876622c0f4b963785712e341b0675a1158ea071cdaf
SHA512: 479b3c47c843aad00c84f34ba4c5969df2ed465957250f0c29fb89b54dd0499522da66249f8e89cf261a6a280e440007e33c31614e4861ae9e413eb44145934d
Homepage: https://metacpan.org/release/Object-ForkAware
Description-en: module to make an object aware of process forks and threads
Object::ForkAware invisibly wraps your object and makes it fork-aware,
automatically checking $$ on every access and recreating the object if the
process id changes. (The object is also thread-aware; if the thread id
changes, the object is recreated in the same manner.)
.
The object can be safely used with type checks and various type constraint
mechanisms, as isa() and can() respond as if they were being called against
the contained object itself.
.
Rationale: If you've ever had an object representing a network connection to
some server, or something else containing a socket, a filehandle, etc, and
used it in a program that forks, and then forgot to close and reopen your
socket/handle etc. in the new process, you'll know what chaos can ensue.
Depending on the type of connection, you can have multiple processes trying
to write to the same resource at once, or simultaneous reads getting each
other's data, dogs and cats living together... It's horrible, and it's an
easy problem to run into.
Description-md5: 05526b95e2108082441ae295b3c6e0aa
Architecture: all
Version: 0.005-1.1
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 30
Depends: perl:any
Filename: pool/universe/libo/libobject-forkaware-perl/libobject-forkaware-perl_0.005-1.1_all.deb
Size: 10252
MD5sum: 025f1089434800e0394cd036c0a9f0d3
SHA1: b468f61112007c2e5c6d51f62304ee318c214797
SHA256: f4caa98a6953d17b907cd876622c0f4b963785712e341b0675a1158ea071cdaf
SHA512: 479b3c47c843aad00c84f34ba4c5969df2ed465957250f0c29fb89b54dd0499522da66249f8e89cf261a6a280e440007e33c31614e4861ae9e413eb44145934d
Homepage: https://metacpan.org/release/Object-ForkAware
Description-en: module to make an object aware of process forks and threads
Object::ForkAware invisibly wraps your object and makes it fork-aware,
automatically checking $$ on every access and recreating the object if the
process id changes. (The object is also thread-aware; if the thread id
changes, the object is recreated in the same manner.)
.
The object can be safely used with type checks and various type constraint
mechanisms, as isa() and can() respond as if they were being called against
the contained object itself.
.
Rationale: If you've ever had an object representing a network connection to
some server, or something else containing a socket, a filehandle, etc, and
used it in a program that forks, and then forgot to close and reopen your
socket/handle etc. in the new process, you'll know what chaos can ensue.
Depending on the type of connection, you can have multiple processes trying
to write to the same resource at once, or simultaneous reads getting each
other's data, dogs and cats living together... It's horrible, and it's an
easy problem to run into.
Description-md5: 05526b95e2108082441ae295b3c6e0aa