How to Install and Uninstall perl-Thread-Semaphore.noarch Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: November 30,2024

1. Install "perl-Thread-Semaphore.noarch" package

Please follow the steps below to install perl-Thread-Semaphore.noarch on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                perl-Thread-Semaphore.noarch
            
                    
    
    Copied

2. Uninstall "perl-Thread-Semaphore.noarch" package

Please follow the instructions below to uninstall perl-Thread-Semaphore.noarch on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                perl-Thread-Semaphore.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the perl-Thread-Semaphore.noarch package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 0:31:38 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : perl-Thread-Semaphore
Version : 2.13
Release : 480.el9
Architecture : noarch
Size : 18 k
Source : perl-5.32.1-480.el9.src.rpm
Repository : ubi-9-appstream-rpms
Summary : Thread-safe semaphores
URL : https://www.perl.org/
License : GPL+ or Artistic
Description : Semaphores provide a mechanism to regulate access to resources. Unlike locks,
: semaphores aren't tied to particular scalars, and so may be used to control
: access to anything you care to use them for. Semaphores don't limit their
: values to zero and one, so they can be used to control access to some resource
: that there may be more than one of (e.g., file handles). Increment and
: decrement amounts aren't fixed at one either, so threads can reserve or return
: multiple resources at once.