@(#)lp.1 1.36 95/10/09 SMI; from SVr4
Copyright 1989 AT&T
Copyright (c) 1995, Sun Microsystems, Inc.
All Rights Reserved
Portions Copyright (c) 1992, X/Open Company Limited
Portions Copyright (c) 1996, Patrick Powell
All Rights Reserved
gsize 10 delim $$ .EN ..
The LPRng \f3lprm client supports an \f3cancel interface when invoked with an \f3cancel program name. This is similar to the ex (1) and vi (1) programs. The supported form of the \f3cancel command arranges for the named \f2jobs to be removed from the specified print queues. The action is identical to that of lprm (1) , including the options, with the difference that the last argument on the command line can be an optional printer name. If the name does not appear in the LPRng printcap database, then the name is assumed to be a job identifier.
The format of request-ID should be either the identifier field value or the job number reported by LPQ.
\f3-P \f2printer\f1 printer name. The destination printer is taken from the command line \f3-P \f2printer\f1 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.
-D " debug-options" Debug options for the program.
15 ID A request ID , as returned by lp . Specifying a request ID cancels the associated request even if it is currently printing.
printer A printer name (for a complete list of printer names, use lpq ). This method may not be supported on all systems, and the -P " printer" form should be used instead.
By default, the destination printer is taken from the command line printer 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:
15 "zero (0)" Successful completion.
"non-zero (!=0)" An error occurred.
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.