Page 301
| /var/spool/output/*/cf* | Daemon control FILES. |
| /var/spool/output/*/df* | Data FILES specified in cf FILES. |
| /var/spool/output/*/tf* | Temporary copies of cf FILES. |
SEE ALSO
lpq(1), lprm(1), pr(1), symlink(2), printcap(5), lpc(8), lpd(8)
HISTORY
The lpr command appeared in BSD 3.
DIAGNOSTICS
If you try to spool too large a file, it will be truncated. lpr will object to printing binary FILES. If a user other than root prints a file and spooling is disabled, lpr will print a message saying so and will not put jobs in the queue. If a connection to lpd(1) on the local machine cannot be made, lpr will say that the daemon cannot be started. DIAGNOSTICS may be printed in the daemon's log file regarding missing spool FILES by lpd(1).
BUGS
Fonts for troff(1) and TeX reside on the host with the printer. It is currently not possible to use local font libraries.
BSD 4, 24 July 1991
lprm—Remove jobs from the line printer spooling queue
SYNOPSIS
lprm [-P printer] [- job # ...] [user ...]
DESCRIPTION
lprm will remove a job, or jobs, from a printer's spool queue. Since the spooling directory is protected from users, using lprm is normally the only method by which a user may remove a job. The owner of a job is determined by the user's login name and hostname on the machine where the lpr(1) command was invoked.
OPTIONS and arguments:
| -P printer | Specify the queue associated with a specific printer; otherwise, the default printer is used. |
| - | If a single - is given, lprm will remove all jobs that a user owns. If the superuser employs this flag, the spool queue will be emptied entirely. |
| user | Causes lprm to attempt to remove any jobs queued belonging to that user (or users). This form of invoking lprm is useful only to the superuser. |
| job # | A user may dequeue an individual job by specifying its job number. This number may be obtained from the lpq(1) program. For example |
lpq _ -l
1st:ken [job#013ucbarpa]
(standard input) 100 bytes
lprm 13
If neither arguments nor OPTIONS are given, lprm will delete the currently active job if it is owned by the user who invoked lprm.
lprm announces the names of any FILES it removes and is silent if there are no jobs in the queue that match the request list.
lprm will kill off an active daemon, if necessary, before removing any spooling FILES. If a daemon is killed, a new one is automatically restarted upon completion of file removals.
Page 302
ENVIRONMENT
If the following ENVIRONMENT variable exists, it is utilized by lprm:
| PRINTER | If the ENVIRONMENT variable PRINTER exists, and a printer has not been specified with the -P option, the default printer is assumed from PRINTER. |
FILES
| /etc/printcap | Printer characteristics file |
| /var/spool/* | Spooling directories |
| /var/spool/*/lock | Lock file used to obtain the pid of the current daemon and the job number of the currently active job |
SEE ALSO
lpr(1), lpq(1), lpd(8)
DIAGNOSTICS
"Permission denied" if the user tries to remove FILES other than his own.
BUGS
Because there are race conditions possible in the update of the lock file, the currently active job may be incorrectly identified.
HISTORY
The lprm command appeared in BSD 3.0.
BSD 4.2, 9 May 1991
lptest—Generate line printer ripple pattern
SYNOPSIS
lptest [length] [count]
DESCRIPTION
lptest writes the traditional "ripple test" pattern on standard output. In 96 lines, this pattern will print all 96 printable ASCII characters in each position. Although originally created to test printers, it is quite useful for testing terminals, driving terminal ports for debugging purposes, or any other task where a quick supply of random data is needed.
The length argument specifies the output line length if the default length of 79 is inappropriate.
The count argument specifies the number of output lines to be generated if the default count of 200 is inappropriate. Note that if count is to be specified, length must also be specified.
HISTORY
lptest appeared in BSD 4.3.
BSD 4.3, 9 May 1991