queue examination program
examines the spooling area used by
for printing files on the
line printer, and reports the status of the specified jobs or all jobs
associated with a user. lpq
invoked without any
arguments reports on any jobs currently in the queue.
The options are as follows:
- Report on the local queues for all printers, rather than
just the specified printer.
- Information about each of the files comprising the job
entry is printed. Normally, only as much information as will fit on one
line is displayed.
- Specify a particular printer, otherwise the default line
printer is used (or the value of the
PRINTER variable in the environment).
All other arguments supplied are interpreted as user names or job numbers
to filter out only those jobs of interest.
For each job submitted (i.e., invocation of
reports the user's name, current rank in the
queue, the names of files comprising the job, the job identifier (a number
which may be supplied to lprm(1)
for removing a specific job), and the total size in bytes. Job ordering is
dependent on the algorithm used to scan the spooling directory and is supposed
to be FIFO (First In First Out). File names comprising a job may be
unavailable (when lpr(1)
is used as
a sink in a pipeline) in which case the file is indicated as “(standard
warns that there is no daemon present (i.e.,
due to some malfunction), the
command can be used to
restart the printer daemon.
If the following environment variables exist, they are used by
- If set to a positive integer, output is formatted to the
given width in columns. Otherwise, lpq
defaults to the terminal width, or 80 columns if the output is not a
- Specifies an alternate default printer.
- To determine printer characteristics.
- The spooling directory, as determined from printcap.
- Control files specifying jobs.
- The lock file to obtain the currently active job.
Unable to open various files. The lock file being malformed. Garbage files when
there is no daemon active, but files in the spooling directory.
appeared in 3BSD
Due to the dynamic nature of the information in the spooling directory,
may report unreliably. Output formatting is
sensitive to the line length of the terminal; this can result in widely spaced