attachment-0001

<DIV>Perhaps this is a little long to explain but I need<BR>to do it this way so you can have a complete idea of<BR>my problem.</DIV> <DIV> </DIV> <DIV>I am in charge of a 25 PC network at the place I work,<BR>23 PCs have Linux installed as Operating System and<BR>2 of them have Windows XP.  The server is also a Linux<BR>box running an application made in Cobol. All the<BR>Linux boxes have SuSE Linux 9.1.</DIV> <DIV> </DIV> <DIV>We have around a dozen matrix printers (Epson FX-890)<BR>connected to some linux stations and a laser printer<BR>(HP LaserJet 1300) connected to one of the windows PCs.</DIV> <DIV> </DIV> <DIV>All the PCs connect to the Linux server through a ssh<BR>session.</DIV> <DIV> </DIV> <DIV>At the Linux Server, all the printers (Linux and Windows)<BR>are declared as remote raw printers so that the users<BR>can print from the Cobol application.</DIV> <DIV> </DIV> <DIV>This server application sends pure text to the remote<BR>printers. At the server, the remote queues are declared<BR>as with CUPS at the Linux PCs and with SMB at the<BR>windows one.</DIV> <DIV> </DIV> <DIV>Each Linux workstation printer has 2 queues defined.<BR>One raw queue called "lp" to receive the jobs sent<BR>by the server and one filtered queue for the local<BR>printing (usually jobs from OpenOffice). This queue<BR>is usually named according to the labour of the user<BR>(sales5, credit2, control1, etc)</DIV> <DIV> </DIV> <DIV>The laser printer connected to the Windows PC works<BR>fine. ALWAYS. The matrix printers work only perfectly<BR>when the user sends a local print job (OpenOffice,<BR>Mozilla, Gimp, etc). The problem is that when the<BR>server sends a raw print job to the remote queues,<BR>frecuently, the printer status turns to "Printer is<BR>not ready" without any reason. This happens more or<BR>less after 3 or 4 print jobs sent to same remote<BR>queue.</DIV> <DIV> </DIV> <DIV>Sometimes the queue looks empty, and some others don't.<BR>The strange thing is that the user gets a complete and<BR>normally printed job, but when the printer turns to the<BR>"Printer is not ready" state, even when the report seems<BR>to be finished, sometimes it still appears in the queue.</DIV> <DIV> </DIV> <DIV>The only way I found to solve this, was creating a<BR>script to modify the /etc/cups/printers.conf file<BR>to turn it to "Printer IS ready" and to restart the<BR>daemon. (CUPS 1.1). This script checks the queue<BR>every minute.</DIV> <DIV> </DIV> <DIV>It doesnt matter if the jobs was still appearing in<BR>the queue, if the printer turned to the "is not ready"<BR>state, it will be printed again when I restart the<BR>daemon!!!  So, if the user is printing numbered<BR>invoices or in a different kind of paper, they waste<BR>resources ans time.</DIV> <DIV> </DIV> <DIV>If the report is quite long (3 or more minutes), the<BR>printer queue will turn again into the "not ready"<BR>state before it finishes and the cron daemon will<BR>restart the cups daemon and I that user will have<BR>3 or more copies of the same report.</DIV> <DIV> </DIV> <DIV>Can anybody lend me a hand?  We were working with<BR>SuSE 8.0 before and this didn't happen. I have this<BR>problem since the upgrade to 9.1</DIV> <DIV> </DIV> <DIV>I think that the "Job Persistence" feature of cups is, in<BR>part, cause of my problem. Do you know how to disable it?<BR>I will appreciate any help anyone can give to me.</DIV> <DIV> </DIV> <DIV>Thanks a lot in advance,</DIV> <DIV> </DIV> <DIV>Martin Schwarzkopf<BR><A>mschwarzkopf@terra.com</A><BR></DIV> <DIV> </DIV> <DIV> </DIV><BR> ___________________________________________________<BR> �Sobre autos lo sabemos todo, y te podemos ayudar!<BR> Ya sea para comprar, vender o comparar autos, entra en el canal de autos de Terra.com<BR> Te aconsejamos, te informamos y te mostramos todo lo que necesitas saber.<BR> <a href="http://www.terra.com/autos">http://www.terra.com/autos</a>