Waiting for printer to finish - error

[Helge Blischke]

Peter Blajev wrote:
> 
> Thank you Helge.
> 
> I'll use hpnpf if I have to, even that I don't like the idea to support
> and depend on one more utility.
> 
> On my systems the socket backend fails on wide
> range of printers. I tested it on almost every type of printer in the
> company and got the same behavior:
> 
>   HP LaserJet 4M Plus
>   HP LaserJet 9000
>   HP LaserJet 9050
>   HP LaserJet 4000
>   HP LaserJet 4050N
>   HP LaserJet 4250N
>   HP LaserJet 2100TN
>   Xerox Docuprint N32
>   Xerox 4230
> 
> Those are only HP and Xerox printers and probably the jetdirect boxes
> are similar but we are using CUPS for 4 years now and with the last
> version we were using 1.1.18 everything worked.
> 
> Regarding this I'm willing to exclude printers as part of the problem.
> 
> I'll see if I can find a work around. :-(
> 
> Any help is appreciated.
> 
> Thanks
> Peter
> 
> PS: Forgot to mention. Tested it on SuSE 7.2 and RedHat Enterprise 3.
> 
> Helge Blischke wrote:
> > Well, it seems that the printer isn't giving anything back to the
> > socket backend. It may well be that the printer requires some more
> > PJL commands to talk back anything (a @PLJ JOB or the like).
> >
> > Your could either edit the printer's PPD and add PJL the
> > appropriate statements to the *JCLBegin: value, or simly use hpnpf
> > as backend:
> >
> >   lpadmin -p sdlpgreg -E -v hpnpf://sdlpgreg:9100
> >
> > You get an additional /var/log/cups/status_log.sdlpgreg file
> > which collects alle the INFO:... lines and, very useful, any
> > messages (including errors) the PostScript interpreter prints
> > to its standard output or standard error.
> >
> > Helge
> >

Well, we abandoned the socket backend in favour of hpnpf because we
needed TBCP
support long before CUPS offered this and never had any problems with
using
hpnpf. 

Helge

-- 
Helge Blischke
Softwareentwicklung
SRZ Berlin | Firmengruppe besscom
http://www.srz.de
tel: +49 30 75301-360