vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi all; I'm trying to use CUPS but we have an odd requirement that it doesn't seem to fulfill: We're using some DOS emulation software called RealNG (printing is configured to use 'lpr'...or any other command line utility) and CUPS prints after a 15-second timeout, whether the job has been closed or not. Is it possible to stop CUPS from closing (and printing) jobs it assumes are finished? If I was using LPRng then I could can specify 'connect_timeout=0' in its configuration file (LPD.conf, I think).. ..but CUPS' implementation of lpr just ignores this as far as I can tell I'm changed from LPRng to CUPS because we're printing to Novel print queues and Windows printer shares, and CUPS handles this beautifuly apart from this seemingly-forced timeout. I'd really appreciate suggestions for a solution. Si Brindley |
| |||
| I had a problem similar to that and solved it by adding one more Linux machine to my network. Its job was to provide an older technology print queue (Not CUPS). Worked for me. I think I used RH 7.0 On Mon, 15 Dec 2003 03:22:34 -0600, Si Brindley wrote: > Hi all; I'm trying to use CUPS but we have an odd requirement that it > doesn't seem to fulfill: We're using some DOS emulation software called > RealNG (printing is configured to use 'lpr'...or any other command line > utility) and CUPS prints after a 15-second timeout, whether the job has > been closed or not. Is it possible to stop CUPS from closing (and > printing) jobs it assumes are finished? > > If I was using LPRng then I could can specify 'connect_timeout=0' in its > configuration file (LPD.conf, I think).. ..but CUPS' implementation of > lpr just ignores this as far as I can tell > > I'm changed from LPRng to CUPS because we're printing to Novel print > queues and Windows printer shares, and CUPS handles this beautifuly > apart from this seemingly-forced timeout. I'd really appreciate > suggestions for a solution. > > Si Brindley |
| |||
| Sergei Izotov <damronhouse@yahoo.com> writes: ]I had a problem similar to that and solved it by adding one more Linux ]machine to my network. Its job was to provide an older technology print ]queue (Not CUPS). Worked for me. I think I used RH 7.0 No need to use another machine. It is easy enough to just put on an "older technology print queue" even an lpd (not lprng) queue onto a new system.. But he wants cups to work. ]On Mon, 15 Dec 2003 03:22:34 -0600, Si Brindley wrote: ]> Hi all; I'm trying to use CUPS but we have an odd requirement that it ]> doesn't seem to fulfill: We're using some DOS emulation software called ]> RealNG (printing is configured to use 'lpr'...or any other command line ]> utility) and CUPS prints after a 15-second timeout, whether the job has ]> been closed or not. Is it possible to stop CUPS from closing (and ]> printing) jobs it assumes are finished? ]> ]> If I was using LPRng then I could can specify 'connect_timeout=0' in its ]> configuration file (LPD.conf, I think).. ..but CUPS' implementation of ]> lpr just ignores this as far as I can tell ]> ]> I'm changed from LPRng to CUPS because we're printing to Novel print ]> queues and Windows printer shares, and CUPS handles this beautifuly ]> apart from this seemingly-forced timeout. I'd really appreciate ]> suggestions for a solution. ]> ]> Si Brindley |
| ||||
| Sergei and all, Hmmm.. ..perhaps another machine is an option.. ..the main problem is that CUPS overwrites the original print queue commands like LPR. If I could use them on another machine before they get to CUPS, that might work. But - the reason I'm using CUPS is that the printers are Novell print queues and a Windows IPP printer. If I could figure out how to make the new machine print to CUPS printers (IPP, right?) on the original machine without using CUPS then I guess that would solve the problem. But how to print to CUPS printers without installing CUPS? - Simon Brindley "Sergei Izotov" <damronhouse@yahoo.com> wrote in message news > I had a problem similar to that and solved it by adding one more Linux > machine to my network. Its job was to provide an older technology print > queue (Not CUPS). Worked for me. I think I used RH 7.0 > > > > On Mon, 15 Dec 2003 03:22:34 -0600, Si Brindley wrote: > > > Hi all; I'm trying to use CUPS but we have an odd requirement that it > > doesn't seem to fulfill: We're using some DOS emulation software called > > RealNG (printing is configured to use 'lpr'...or any other command line > > utility) and CUPS prints after a 15-second timeout, whether the job has > > been closed or not. Is it possible to stop CUPS from closing (and > > printing) jobs it assumes are finished? > > > > If I was using LPRng then I could can specify 'connect_timeout=0' in its > > configuration file (LPD.conf, I think).. ..but CUPS' implementation of > > lpr just ignores this as far as I can tell > > > > I'm changed from LPRng to CUPS because we're printing to Novel print > > queues and Windows printer shares, and CUPS handles this beautifuly > > apart from this seemingly-forced timeout. I'd really appreciate > > suggestions for a solution. > > > > Si Brindley |