[KLUG Members] printing and Linux

[Adam Tauno Williams]

>> > But in Linux once print job is fired it is lost in black hole.
>> Never.  I haven't "lost" a print job on LINUX in years and years.  I can
>> go into the printer server via a nice web interface and reprint a job
>> that I successfully printed 24 hours ago.
> This has never worked for me.  Always get "client-error-forbidden" in
> the web browser when trying.  Sure would like to know the fix.

It has to do with the permissions setup in the cups configuration file;  I'll
take a look when I get a minute.

>>   Or I can hold a printer and
>> jobs will nicely accumulate for weeks.
> I've lost jobs.  Lost considerably less since:  I stopped trying to have
> reduntant cups servers serving up the same printer and changed one
> particular problem printer from a jetdirect connection to a smb://
> connection.

I never tries redundant servers,  I just buy a bigger server as I only 
want one
print server. :)  Otherwise you are loosing jobs at the DEVICE, and 
nothing can
help if the device doesn't NACK the server.  We used to loose print jobs to
serial printers connected via Cisco 2511 access servers, but twiddling around
inside the Ciscos fixed that problem.

> Also occasionally will lose a barcode print job that goes through an
> ltsp jet direct style port (9100).  The only way I have found to fix is
> to reboot the ltsp client and the jobs are always lost.

Does the LTSP device actually queue stuff?   Our label printers are serial and
all our laser printers now support IPP;  IPP all-the-way-down-the-wire is very
nice.   Restarting the queue in CUPS actually resets the printer - it says
"Reseting..." on the little LCD panel.