Hi Y'all,
Ah, USENET, its not just a technology, its a philosophy
(and a darn correct one).
Thanks to all who answered my call for help with the lprm
command. G.Bell@comp.brad.ac.uk hit it right on the money. Here was my
original posting:
>> Anyone know the magic of getting the lprm command under Sun OS 4.1.1
>> to dequeue a print job that is queued on a remote machine?
>>
>> It seems that once the local machine spools the job to the print server
>> (ie., to rm=PRINTERSERVERHOST in /etc/printcap) that the lprm command becomes
>> useless. Anyone know a fix for this?
And here is the fix:
The reason that the lprm command will not delete a file that
is remotely queued on the server is because of a mal-formed printcap
entry on the clients printcap file.
Here is the change that need to be made. I will use a snipet
from a client side /etc/printcap and the entry for "myPrinter" as an
example:
-------------- wrong printcap entry ----------------
myPrinter:\
:lp=/dev/null:\
:rm=PRINTERSERVERHOST:\
:rp=myPrinter:\
:sd=/usr/spool/myPrinter:\
:lf=/usr/spool/myPrinter/log:
-------------- correct printcap entry ----------------
myPrinter:\
:lp=:\
:rm=PRINTERSERVERHOST:\
:rp=myPrinter:\
:sd=/usr/spool/myPrinter:\
:lf=/usr/spool/myPrinter/log:
The difference is in the 2nd line. The "lp=/dev/null" entry
will evidently make the "lprm" command on the client think that the
spool for the printer is on the "client" machine and not on the
"server" machine (ie., lprm will not attempt to contact the lpd
daemon on the server machine). This is the cause of the problem.
If you make the change this problem is fixed. There is no need
to restart the lpd daemon on either the client or the server.
Thanks again to all who responded.
- Joe
-- --------------------------------------------------------------- Joe Bush bush@fremont.ssc.gov System Administrator Office: 214-708-3497 Superconducting Super Collider Laboratory 2550 Beckleymeade Ave, MS 4005, Dallas, TX. 75237
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:52 CDT