To obtain pre-compiled binaries for lp and lpstat, install the cups-client package using your distribution’s package manager. On Debian-based systems, use sudo apt install cups-client, while Red Hat-based systems require sudo yum install cups-client. These packages provide the essential command-line utilities required to manage network printers without compiling software from source.
Understanding the Role of CUPS Client
Thelp and lpstat commands are fundamental components of the Common Unix Printing System (CUPS). While CUPS is primarily known as a printing system server, the client tools are separated into distinct packages in many modern Linux distributions. This separation allows users who only need to send print jobs or check printer status to avoid installing the full server suite, which includes daemon processes and administrative interfaces.
When you encounter missing binary errors such as command not found: lp, it indicates that the client utilities are not present on your system. This often happens in minimal installations, container environments, or servers configured solely as print clients rather than servers. The solution is straightforward: install the specific package that contains these binaries. There is no need to download tarballs or compile code manually, as every major distribution maintains stable, pre-compiled versions of these tools.
For more context on managing network printer configurations, you might find Getting Path Name of Driver Used for Network Printer LPR-UPS on Linux Ubuntu 22.04 Server useful, as it details how drivers interact with the underlying CUPS infrastructure once the client tools are available.
Installing on Debian and Ubuntu Systems
On Debian-based distributions, including Ubuntu, Linux Mint, and Kali Linux, thecups-client package is available in the default repositories. The installation process is simple and relies on the Advanced Package Tool (APT). First, ensure your package index is up to date by running sudo apt update. Then, install the client with the following command:
sudo apt install cups-clientlp, lpq, lprm, and lpstat along with any necessary dependencies. In some newer versions of Ubuntu, the cups-client package may be pulled in automatically when you install other printing-related packages, but explicitly installing it guarantees its presence. After installation, verify the success by checking the version of the lp command:
lp --versionInstalling on RHEL, CentOS, and Fedora
Red Hat Enterprise Linux (RHEL), CentOS, and Fedora systems handle CUPS components differently. Historically, these binaries were part of the maincups package. However, in recent releases, they are often contained within cups-client or cups-libs depending on the specific version and repository configuration. To ensure you get the correct binaries, start by updating your package database:
sudo yum updatesudo dnf updatesudo yum install cups-clientcups package, which typically includes the client utilities in older or strictly server-focused configurations:
sudo yum install cupslpstat -V. This command checks the version of the local CUPS client and confirms that the binary is accessible in your PATH.
Verifying Installation and Functionality
Once the package is installed, it is crucial to verify that the commands are not only present but also functional. Runlpstat -p to list all printers known to the system. If the command returns a list of printers or an empty list without error, the client is working correctly. If you receive permission denied errors, ensure your user account is part of the appropriate groups, such as lpadmin, although basic query commands usually work for standard users.
For troubleshooting connectivity issues with specific network printers, refer to Troubleshooting curl not working on an RHEL8 Server, as network diagnostics often overlap when dealing with remote printing services.
Frequently Asked Questions
Why do I get "command not found" for lp even after installing CUPS?
This occurs because the CUPS server package does not always include the client utilities in minimal installations. You must explicitly install the cups-client package to gain access to lp and lpstat. Always check your distribution's documentation for the exact package name.
Can I use these binaries on macOS?
No, macOS uses a different printing architecture based on BSD print commands like lpr and lpq. While the syntax is similar, the underlying implementation differs. You cannot simply install cups-client on macOS to get native support; instead, rely on the built-in CUPS framework provided by Apple.
Do I need root privileges to run lpstat?
Generally, no. Standard users can run lpstat to view queue status and printer information. However, administrative actions like adding or removing printers via lpadmin require elevated privileges. If lpstat fails for a regular user, check file permissions on the CUPS socket.
What if my package manager says cups-client is not found?
This suggests your system repositories are outdated or misconfigured. Update your package lists first. If the issue persists, try installing the generic cups package, which often bundles the client tools in older distributions. Ensure you are connected to the internet during the update process.
Are there alternative tools to lp and lpstat?
Yes, you can use lpr and lprng utilities, which are part of the LPD protocol. However, lp is the standard for CUPS-based systems and offers better integration with modern network printers. Switching to LPD tools may result in lost functionality regarding job tracking and driver-specific options.