rlprm(1) | UNIX Reference Manual | rlprm(1) |
rlprm - remove jobs from a remote line printer spooling queue
rlprm [-qNV] [-Hprinthost] [-Pprinter] [-Xproxyhost] [--debug] [--timeout=seconds] [--port=port] [-] [ job # ... ] [ username ... ]
rlprm uses TCP/IP to remove jobs you own from printers anywhere on a network. Unlike lprm, it does not require that the remote printers be explicitly known to the local system (traditionally through /etc/printcap), and thus is considerably more flexible and requires less administration.
rlprm can be used anywhere a traditional lprm might be used, and is backwards compatible with traditional BSD lprm. If rlprm is invoked as lprm, it preserves all known lprm semantics, with the exceptions of those semantics mentioned in BUGS / LIMITATIONS below.
rlprm can be set up, installed, and used in the same two ways as rlpr(1) (that is, either with or without the rlprd(8) proxy daemon). Please see rlpr(1) for details, and to see whether you will need to use the rlprd(8) proxy daemon or not.
Instead of using -H, one can specify the hostname directly including it with the printer name with the printer@hostname syntax.
The following environment variables are used by rlprm:
Note that one can also specify the host to examine by setting printer to be printer@hostname. This may be more convenient than setting RLPR_PRINTHOST, but will confuse the traditional BSD print commands.
~/.rlprrc Personal printer/host database /etc/hosts.lpd Host-based security on printhost /etc/hosts.equiv Host-based security on printhost /etc/passwd Personal identification /etc/rlprrc System-wide printer/host database
meem <meem@gnu.org>
Due to limitations in the current lpd protocol, it is not currently possible to tell whether or not the job removal succeeded when operating in silent mode.
Due to limitations in the current lpd protocol, it is not currently possible to emulate the superuser semantics for the `-' option. Instead, only root's jobs are removed.
Due to general niavete in the lpd protocol, rlprm(1) provides a lot of room for misbehavior; it is trivial to imagine how it can be used to remove jobs that do not belong to you. Unfortunately, any security added at this point is just sugar-coating -- the underlying protocol is flawed.
1999/10/28 | rlpr 2.04 |