FC3 RC1 - Networked LPD server printing still not working.

[Michal Jaegermann]

On Tue, Oct 26, 2004 at 11:31:35AM -0500, Satish Balay wrote:
> 
> I prefer LPRng as:
> - I don't need to configure local cupsd/lpd
> - I can tunnel print commands easily through ssh/portforwarding.

'cups' has a serious show-stopper "feature", on the top of various
more or less serious annoyances, if you have an installation with
really remote printers and many users.  Once a job left the
originating machine its status is 'done' and 'lpq' will not tell you
more about its status, nor a job identifier on a remote, and 'lprm'
will not remove it even if it is going to sit in queue for the next
two weeks.  Your "Print Manager" will just show you a happy picture.
Samba is affected too. That is something which never was a problem
for lpr/LPRng.

Findinig 'root' for a print server and asking him/her to do a job
removal for us is not a real option although it seems to be
proffered for example here:

http://thread.gmane.org/gmane.comp.printing.cups.general/1989

<quote>
If you want to cancel a job which is on the server,
you must do it on the server and you must use
the server's job id:
  cancel -h SERVER SERVER'S_JOB_ID
</quote>

If I am misinterpreting what this is saying, and I can really do
that from the originating machine ("SERVER" may not have a shell
login at all), then at least GUI interface for print jobs management
is buggy because it is not doing that for me; but in any case why I
should worry about what is "SERVER" and how a remote queue happen to
be called in the given moment?  Apparently I need the last piece of
that puzzle for 'lpstat'.  This may be changing outside of my
control and after all I submitted a print job to a local queue.

Checking possiblity that I do not understand and I should really use
these commands from a submitting account I tried, proposed in the
quoted message from comp.printing.cups.general,

  lpstat -h SERVER -o QUEUE

(with names for "SERVER" and "QUEUE" I happen to know).   I only
got back: "lpstat: Unable to connect to server: Connection refused."
Just lovely!  'cancel -h ...' as above, after I checked that job
id on a server, responded with "Uknown destination".  Yes, I can
print.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90619
ellicited only a comment that apparently this is how this is
"supposed" to be.  Ugh!

   Michal