How to Install and Uninstall task-spooler Package on Ubuntu 21.10 (Impish Indri)

Last updated: February 17,2025

1. Install "task-spooler" package

Please follow the guidelines below to install task-spooler on Ubuntu 21.10 (Impish Indri)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                task-spooler
            
                    
    
    Copied

2. Uninstall "task-spooler" package

Learn how to uninstall task-spooler on Ubuntu 21.10 (Impish Indri):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                task-spooler
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the task-spooler package on Ubuntu 21.10 (Impish Indri)

Package: task-spooler
Architecture: amd64
Version: 1.0.1+dfsg1-1
Priority: optional
Section: universe/misc
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Alexander Inyukhin
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 93
Depends: libc6 (>= 2.15)
Filename: pool/universe/t/task-spooler/task-spooler_1.0.1+dfsg1-1_amd64.deb
Size: 34388
MD5sum: a61e81c54d38d0d78eb28374c68ca041
SHA1: de33b3470c9b53ae6e8c1ba5514043890e3657ea
SHA256: 04daf5eed05504204290ebd14381be19580a90076dce9ccc8357287370eb59de
SHA512: 6d24d156e112362f93ae72c01a12880435647dc89e606dcb87be49bbcad16f3ac6a8fc9475104953f10701ceb95f5d10c57b7c06b996a1471e1bf0fb87c63419
Homepage: https://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