>> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, March 03, 2004 11:23 PM >> To: [EMAIL PROTECTED] >> Subject: RE: LPRng: After upgrade still Stalling remote printers >> >> >> >> -----Original Message----- >> >> From: Shawn Clark [mailto:[EMAIL PROTECTED] >> >> Sent: Monday, March 01, 2004 10:00 AM >> >> To: [EMAIL PROTECTED] >> >> Subject: LPRng: After upgrade still Stalling remote printers >> >> >> >> >> >> Hello, >> >> >> >> We have several printers attached to Linksys Print Servers. >> >> When multiple >> >> jobs are spooled through LPRng the print queues seem to >> hang up and go >> >> into "stalled" state. Removing the printjobs from the queue >> >> seems to be >> >> the only way to get these print queues working properly again. >> >> >> >> While the LPRng print queue is stalled, MS Windows is able to print >> >> directly to the Linksys devices. >> >> >> >> Any help would be greatly appreciated. >> >> >> >> We are running Debian/Sid - LPRng-3.8.25. >> >> >> >> Here is my printcap entry and lpq output for this printer >> while it is >> >> stalled: >> >> >> >> .common: >> >> :sd=/var/spool/lpd/%P >> >> :lf=/var/spool/lpd/%P/log >> >> :af=/var/spool/lpd/%P/acct >> >> :sh:mx=0:mc=0 >> >> >> >> sea-ps-24-p1|lp1 >> >> :cm=(Back Office)Okidata ML391 Plus @ SEA-PS-24 on Port 1:\ >>> :tc=.common >> >> :[EMAIL PROTECTED] >> >> >> >> >> >> # lpq -P sea-ps-24-p1 >> >> >> >> Printer: [EMAIL PROTECTED] '(Back Office)Okidata ML391 Plus @ >> >> SEA-PS-24 on Port 1' (dest [EMAIL PROTECTED]) >> >> Queue: 8 printable jobs >> >> Server: pid 7168 active >> >> Unspooler: pid 7322 active >> >> Status: waiting for subserver to exit at 13:10:09.756 >> >> Rank Owner/ID Class Job Files >> >> Size Time >> >> stalled(1757sec) [EMAIL PROTECTED] A 792 >> smbprn.001697.L2b079 19804 >> >> 12:22:46 >> >> 2 [EMAIL PROTECTED] A 815 >> smbprn.001698.rSE4Xe 19804 >> >> 12:23:14 >> >> 3 [EMAIL PROTECTED] A 836 >> smbprn.001699.IMePPy 19804 >> >> 12:24:47 >> >> 4 [EMAIL PROTECTED] A 12 >> smbprn.001700.FtF9lg 19804 >> >> 12:34:00 >> >> 5 [EMAIL PROTECTED] A 38 >> smbprn.001701.izWmGI 19804 >> >> 12:36:21 >> >> 6 [EMAIL PROTECTED] A 57 >> smbprn.001703.gyxopI 19804 >> >> 12:36:54 >> >> 7 [EMAIL PROTECTED] A 72 >> smbprn.001705.0U21rL 19804 >> >> 12:38:21 >> >> 8 [EMAIL PROTECTED] A 733 >> smbprn.001710.lE0LvC 10024 >> >> 13:07:29 >> >> (LPD Server): >> >> (P1)STATE: Idle >> >> TYPE: Parallel >> >> PRINTER STATUS: On-Line >> >> >> >> >> > Shawn, >> > >> > Should [EMAIL PROTECTED] instead of [EMAIL PROTECTED] >> > >> > "(P1)STATE: Idle" Makes me think that... >> > >> > I have a USB printer on a Linksys printserver, >> > and the printer is listed as "\\PRINTSERVER\P1". >> > It has 3 logical ports available, but I don't >> > know what they'd be labeled. >> > >> > Jim >> > >> >> >> Hi Jim, >> >> Thanks for reading my post. I was beginning to wonder if my >> question was >> covered somewhere obvious that I must have overlooked a dozen >> times trying >> to figure this one out. >> >> I didn't test useing P1 instead of L1(logical port 1) for the >> print queue >> name, but Im pretty sure that is not the problem. I believe >> the problem >> is that the Linksys print servers are complete pieces of >> SH*T! I put an >> Intel NetExpressPro print server in one of the Linksys' place >> and it works >> with no problems. In fact where, with the Linksys, when I >> spool 6 small >> jobs(printcap file with 8 entries) one right after the other, >> they stack >> up in LPRng's spool and then hang that print queue...with the >> Intel the >> jobs don't hang around in the queue long enough to be >> detected by lpc or >> lpq....they get fired off to the Intel unit and print out with no >> problems. >> >> It would be interesting to know how this Linksys device could >> cause the >> LPRng queue to stall.....anyone? >> >> Cheers, >> >> shawn >> > If the printer is attached to P1 (the physical > printer port, and you're trying to send > the print jobs to a different port (L1), > LPRng is going to hang the jobs-you're never > going to see them print. > > The Windows PCs are sending the jobs to the correct > port; that's why they can print while LPRng > isn't. > > What model Linksys Print Server is it? > > Jim > > > > > > You might try the lpc kill command. I have found that this will restart > the queue and try to print all the jobs in the queue. > > lpc kill "print queue name" > > > > Thanks, > Tom > 847-647-3507 > > >
I have tried this, and sometimes I get some results. For instance, one job might come out but the queue stalls again on the next job. Ultimately this is not a solution, even if it worked 100% of the time. I can't be 'lpc killing' these poor bastards printserver 4 times a day, we both have better things to do than that! :) I can't imagine why the Linksys PS would cause LPRng to act this way, but it would be nice to know the answer. Meanwhile I think I will be replacing the pice of shite Linksys devices with some old Intel NetExpress Pro's. They work great with virtually no screwing with them. shawn ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
