Why does CUPS print after 15 seconds whether the job is ready or not?
Hi there,
I have not managed to find a solution to my problem after a long search on the 'Net. Basically we were using LPRng to print to a couple of
Novell-hosted LaserJets and a Windows-hosted Deskjet from RealNG. RealNG is basically a DOS emulator that runs on Linux.. ..it can use any command line you choose to print, so we've been using:
lpr -P <printername> <filename>
...which worked fine except that, if the DeskJet's Windows PC was off, the print jobs would get lost.
So, we changed to printing with CUPS so that print jobs could be managed (and they now wait for the Windows PC to come back online). This has worked well to both the DeskJet (via IPP) and the LaserJets (using a backend script for CUPS called 'ncp', which just uses 'nprint'). However (and here's the point of my question) - there seems to be a forced timeout of about 15 seconds in CUPS. If we start a printjob in our DOS software and haven't finished adding to it, CUPS prints after 15 seconds whether it's been told to or not.
With LPRng, it seems lpr would reference the lpd.conf file where we could specify 'connect_timeout = 1000' or 'connect_timeout = 0' - but I can't find an equivilent fix for CUPS and its version of lpr seems to ignore the
lpd.conf file (and the printcap file).
If anyone can suggest a solution it would be much appreciated. Many thanks,
Simon.
|