How to Install and Uninstall task-spooler Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: May 21,2024

1. Install "task-spooler" package

Please follow the steps below to install task-spooler on Ubuntu 20.10 (Groovy Gorilla)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                task-spooler
            
                    
    
    Copied

2. Uninstall "task-spooler" package

Here is a brief guide to show you how to uninstall task-spooler on Ubuntu 20.10 (Groovy Gorilla):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                task-spooler
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the task-spooler package on Ubuntu 20.10 (Groovy Gorilla)

Package: task-spooler
Architecture: amd64
Version: 1.0-1
Priority: optional
Section: universe/misc
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Alexander Inyukhin
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 85
Depends: libc6 (>= 2.15)
Filename: pool/universe/t/task-spooler/task-spooler_1.0-1_amd64.deb
Size: 33438
MD5sum: ededfd0103d034efc4dbbc446a3e7333
SHA1: efcb59659b7b8cb81c38a2901f5ec3d82bc4c826
SHA256: a4d32c569b13f1b4488b19ae6a46683fcd38c0caa2ac1c6d036f4ea086182449
SHA512: c842d4687df5bb6570fbdc4f4d6c2760c60b0268dfe3397f92b2d4a4f7dd6f78316d9c79c512dbccb5df5083339c6980f78385826086bfb82223c6296ffa3d21
Homepage: http://viric.name/soft/ts/
Description-en: personal job scheduler
Task spooler is a Unix batch system where the tasks spooled run one
after the other. Each user in each system has his own job queue. The tasks are
run in the correct context (that of enqueue) from any shell/process, and its
output/results can be easily watched. It is very useful when you know that
your commands depend on a lot of RAM, a lot of disk use, give a lot of
output, or for whatever reason it's better not to run them at the same time.
Description-md5: 2770bf2e5456ac7ac05f66f704bece4d