lpstat - print information about the status of the LP print service
If no options are given, then lpstat prints the status of all the user's print requests made by lp on the default printer. (see lp(1) and lpr(1)). Any arguments that are not options are assumed to be request-IDs as returned by lp or printer names. The lpstat command prints the status of such requests. The options may appear in any order and may be repeated and intermixed with other arguments. Some of the keyletters below may be followed by an optional list that can be in one of two forms: a list of items separated from one another by a comma, or a list of items separated from one another by spaces enclosed in quotes. For example:
Specifying all after any keyletter that takes list as an argument causes all information relevant to the keyletter to be printed. For example, the command:
prints the status of all output requests.
The omission of a list following such key letters causes all information relevant to the key letter to be printed. For example, the command:
prints the status of all output requests.
By default, the destination printer is taken from the command line dest value, then the environment variables PRINTER, LPDEST, NPRINTER, NGPRINTER, then first entry in the printcap information, and and finally the default_printer entry from the configuration file, and then the compile time default.
The following exit values are returned:
The files used by LPRng are set by values in the printer configuration file. The following are a commonly used set of default values.
/etc/lpd.conf LPRng configuration file
${HOME}/.printcap user printer description file
/etc/printcap system printer description file
/etc/lpd.perms printer permissions
/var/spool/printer* spool directories
/var/spool/printer*/printer lock file for queue control
/var/spool/printer*/control.printer queue control
/var/spool/printer*/active.printer active job
/var/spool/printer*/log.printer log file
Most of the diagnostics are self explanatory. If you are puzzled over the exact cause of failure, set the debugging level on (-D5) and run again. The debugging information will help you to pinpoint the exact cause of failure.
|
Закладки на сайте Проследить за страницей |
Created 1996-2025 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |