1.ds VE LPRng-3.9.0
2.TH LPRM 1 \*(VE "LPRng"
3.ig
4lprm.1,v 3.39 1998/03/29 18:37:49 papowell Exp
5..
6.SH NAME
7lprm \- remove jobs from the line printer spooling queue
8.SH SYNOPSIS
9.B lprm
10[
11.B \-a
12]
13[
14.B \-A
15]
16[
17.BI \-D debugopt
18]
19[
20.BI \-P printer
21]
22[
23.B \-V
24]
25[
26.BI \-U user
27]
28.ti +5n
29[
30.IR jobid \|.\|.\|.
31]
32[
33.I all
34]
35.SH DESCRIPTION
36.PP
37.I Lprm
38will send a request to the LPD server to remove jobs
39from a spool queue.
40(See
41.IR clean (1)
42for an
43.IR lp (1)
44compatible interface.)
45.I Lprm
46is normally the only method by which a user may remove a job.
47The jobs to be removed are specified by the job number or user name;
48with no specifiers the first removable in a queue will be
49selected for removal.
50Usually users may only remove jobs submitted by themselves from
51the host which originated the original lpr request.
52.PP
53The spool queue is searched first for jobs that the user has permissions to
54remove,
55then for jobs that match any of the specified set of tags.
56If no tags are specified,
57only the first job in the queue that the user has permissions to remove
58will be removed.
59If the
60.B \-a
61flag or the
62.I all
63spool queue is specified,
64.I lprm
65will search all available spool queues.
66.LP
67The
68.I all
69wildcard jobid is used to match all jobs in a spool queue;
70however unless the user has
71.I control
72permissions  for the spool queue only the user's jobs will be removed.
73See the
74.BR lpd (1)
75man page for details about control permissions.
76.PP
77A jobid can be a job number,
78a user name,
79a job identifier,
80or a pattern for a
81.I glob
82based wild card match.
83This match is applied to the job identifier information.
84.PP
85.I Lprm
86will announce the names of any files it removes and is silent if
87there are no jobs in the queue which match the request list.
88If the job being removed is active,
89the LPD server will stop printing the job and then
90restart printing operations.
91.SH EXAMPLES
92.TP
93Remove the last job I submitted if it is in the queue:
94.sp
95lprm
96.TP
97Remove job 25 in spool queue p1:
98.sp
99lprm -Pp1 25
100.TP
101Remove job 25 and 30 in spool queue p1:
102.sp
103lprm -Pp1 25 30
104.TP
105Remove all of user john's jobs in spool queue p1:
106.sp
107lprm -Pp1 john
108.TP
109Remove all jobs in spool queue p1:
110.sp
111lprm -Pp1 all
112.TP
113Remove all jobs in all spool queues:
114.sp
115lprm -a all
116.TP
117Remove the jobs with identifier nobody@system in spool queue p1.
118Note that the quotes around the pattern are needed to suppress
119shell glob expansion.
120.sp
121lprm -Pp1 'nobody@system*'
122.SH OPTIONS
123.IP "\fB\-A\fR" 5
124Use authentication specified by the value of the AUTH environment variable.
125.IP "\fB\-a\fR" 5
126Remove files from all spool queues available to the user.
127.IP "\fB\-P\fIprinter\fR" 5
128Specifies printer queue.
129By default,
130the destination printer
131is taken from
132the command line
133.I dest
134value,
135then
136the environment variables
137PRINTER,
138LPDEST,
139NPRINTER,
140NGPRINTER,
141then first entry in the printcap information,
142and and finally the default_printer entry from the
143configuration file,
144and then the compile time default.
145.IP "\fB\-U\fIuser\fR" 5
146Explicitly provide a userid for doing the removal to the LPD server.
147This can be done only by ROOT or userids listed in the
148.I allow_user_setting
149configuration or printcap option.
150This facility is provided to allow printing front end systems such
151as SAMBA to submit job removal requests on behalf of users.
152.IP "\fB\-D\fIdebugopts\fR" 5
153Debugging is controlled using the
154.B \-D
155option. This accepts a comma-separated list of debugging
156settings. These settings take one of two forms: 
157.B facility=value , 
158or
159.B value 
160to set an overall default value.
161.IP "\fB\-V\fR" 5
162The \-V option prints the version information for the program and
163verbose information about activities.
164.SH WARNINGS
165.PP
166Users with
167CONTROL (i.e.- administrative) permissions on spool queues
168can remove any or all jobs.
169The
170.I all
171wildcard defaults to all user jobs,
172not just those submitted by the user.
173This allows administrators to purge a spool queue easily.
174.SH ENVIRONMENT
175.PP
176By default,
177the destination printer
178is taken from
179the command line
180.I dest
181value,
182then
183the environment variables
184PRINTER,
185LPDEST,
186NPRINTER,
187NGPRINTER,
188then first entry in the printcap information,
189and and finally the default_printer entry from the
190configuration file,
191and then the compile time default.
192.SH "EXIT STATUS"
193.PP
194The following exit values are returned:
195.TP 15
196.B "zero (0)"
197Successful completion.
198.TP
199.B "non-zero (!=0)"
200An error occurred.
201.SH FILES
202.PP
203The files used by LPRng are set by values in the
204printer configuration file.
205The following are a commonly used set of default values.
206.nf
207.ta \w'/var/spool/lpd/printcap.<hostname>           'u
208_LPD_CONF_PATH_	LPRng configuration file
209${HOME}/.printcap	user printer description file
210_PRINTCAP_PATH_	printer description file
211_LPD_PERMS_PATH_	permissions
212_LOCKFILE_	lock file for queue control
213/var/spool/lpd		spool directories
214/var/spool/lpd/QUEUE/control	queue control
215/var/spool/lpd/QUEUE/log	trace or debug log file
216/var/spool/lpd/QUEUE/acct	accounting file
217/var/spool/lpd/QUEUE/status	status file
218.fi
219.SH "SEE ALSO"
220lpd.conf(5),
221lpc(8),
222lpd(8),
223checkpc(8),
224lpr(1),
225lpq(1),
226lprm(1),
227printcap(5),
228lpd.conf(5),
229pr(1), lprng_certs(1), lprng_index_certs(1).
230.SH DIAGNOSTICS
231.nf
232Most of the diagnostics are self explanatory.
233If you are puzzled over the exact cause of failure,
234set the debugging level on (-D5) and run again.
235The debugging information will 
236help you to pinpoint the exact cause of failure.
237.fi
238.SH "HISTORY"
239LPRng is a enhanced printer spooler system
240with functionality similar to the Berkeley LPR software.
241The LPRng mailing list is lprng@lprng.com;
242subscribe by sending mail to lprng-request@lprng.com with
243the word subscribe in the body.
244The software is available from ftp://ftp.lprng.com/pub/LPRng.
245.SH "AUTHOR"
246Patrick Powell <papowell@lprng.com>.
247