1 .\" Copyright (c) 1983 Regents of the University of California.
2 .\" All rights reserved. The Berkeley software License Agreement
3 .\" specifies the terms and conditions for redistribution.
5 .\" @(#)lprm.1 6.1.1 (2.11BSD) 1996/10/22
7 .TH LPRM 1 "October 22, 1996"
10 lprm \- remove jobs from the line printer spooling queue
24 will remove a job, or jobs, from a printer's spool queue.
25 Since the spooling directory is protected from users, using
27 is normally the only method by which a user may remove a job.
30 without any arguments will delete the currently active job if it is
31 owned by the user who invoked
38 will remove all jobs which a user
39 owns. If the super-user employs this flag, the spool queue will
40 be emptied entirely. The owner is determined by the user's login name
41 and host name on the machine where the
45 Specifying a user's name, or list of user names, will cause
47 to attempt to remove any jobs queued belonging to that user
48 (or users). This form of invoking
50 is useful only to the super-user.
52 A user may dequeue an individual job by specifying its job number.
53 This number may be obtained from the
59 .ta \w'k0-k9 'u +\w'Type 'u +\w'"/usr/sbin/lpd" 'u
60 .ta \w'1st: 'u +\w'(standard input) 'u
63 1st: ken [job #013ucbarpa]
64 (standard input) 100 bytes
70 will announce the names of any files it removes and is silent if
71 there are no jobs in the queue which match the request list.
74 will kill off an active daemon, if necessary, before removing
75 any spooling files. If a daemon is killed, a new one is
76 automatically restarted upon completion of file removals.
80 option may be usd to specify the queue associated with a specific
81 printer (otherwise the default printer, or the value of the PRINTER
82 variable in the environment is used).
85 .ta \w'/usr/spool/*/lock 'u
86 /etc/printcap printer characteristics file
87 /usr/spool/* spooling directories
88 /usr/spool/*/lock lock file used to obtain the pid of the current
89 daemon and the job number of the currently active job
96 ``Permission denied" if the user tries to remove files other than his
99 Since there are race conditions possible in the update of the lock file,
100 the currently active job may be incorrectly identified.