How to Install and Uninstall perl-LockFile-Simple Package on openSuSE Tumbleweed
Last updated: December 28,2024
1. Install "perl-LockFile-Simple" package
In this section, we are going to explain the necessary steps to install perl-LockFile-Simple on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-LockFile-Simple
Copied
2. Uninstall "perl-LockFile-Simple" package
This tutorial shows how to uninstall perl-LockFile-Simple on openSuSE Tumbleweed:
$
sudo zypper remove
perl-LockFile-Simple
Copied
3. Information about the perl-LockFile-Simple package on openSuSE Tumbleweed
Information for package perl-LockFile-Simple:
---------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-LockFile-Simple
Version : 0.208-5.30
Arch : x86_64
Vendor : openSUSE
Installed Size : 39.0 KiB
Installed : No
Status : not installed
Source package : perl-LockFile-Simple-0.208-5.30.src
Upstream URL : http://search.cpan.org/dist/LockFile-Simple/
Summary : Simple file locking scheme
Description :
This simple locking scheme is not based on any file locking system calls
such as 'flock()' or 'lockf()' but rather relies on basic file system
primitives and properties, such as the atomicity of the 'write()' system
call. It is not meant to be exempt from all race conditions, especially
over NFS. The algorithm used is described below in the *ALGORITHM* section.
It is possible to customize the locking operations to attempt locking once
every 5 seconds for 30 times, or delete stale locks (files that are deemed
too ancient) before attempting the locking.
---------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-LockFile-Simple
Version : 0.208-5.30
Arch : x86_64
Vendor : openSUSE
Installed Size : 39.0 KiB
Installed : No
Status : not installed
Source package : perl-LockFile-Simple-0.208-5.30.src
Upstream URL : http://search.cpan.org/dist/LockFile-Simple/
Summary : Simple file locking scheme
Description :
This simple locking scheme is not based on any file locking system calls
such as 'flock()' or 'lockf()' but rather relies on basic file system
primitives and properties, such as the atomicity of the 'write()' system
call. It is not meant to be exempt from all race conditions, especially
over NFS. The algorithm used is described below in the *ALGORITHM* section.
It is possible to customize the locking operations to attempt locking once
every 5 seconds for 30 times, or delete stale locks (files that are deemed
too ancient) before attempting the locking.