Bug 18853 - LPD running several times - hanging printer queues
Summary: LPD running several times - hanging printer queues
Keywords:
Status: CLOSED DUPLICATE of bug 11740
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lpr
Version: 6.2
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-10 21:05 UTC by sound
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-10-10 21:05:49 UTC
Embargoed:


Attachments (Terms of Use)

Description sound 2000-10-10 21:05:31 UTC
Having problem printing to network printers.  The jobs hang in the queue.  
when running 'lpc stat <printername>' jobs show as waiting.  When I 
run 'ps -ef |grep lpd' - 'lpd' shows as running more than once (usually 
twice).  If I kill the second instance, the reports will occasionally 
print.  Often it is a matter of a combination of killing the process, and 
trying 'lpc restart <printername>' or 'lpc down/up <printername>'.  I have 
not found consistency in getting the reports to print.
I had a file sent to me - lpr-0.50-7.i386.rpm - installed that.  It seems 
to help a little, but we still have a problem.
There are only 3 of 18 printers that get hung.  They are all at the bottom 
in printtool, but were not to start.  I deleted and re-added 2 of them.  I 
have also swapped hardware on one of them.  The 3 printers are HP 
laserjets - a model 4, 5, & 4050N.  The 4050N has a built in network card, 
the other 2 are using NetGear PS104 print servers.  I have them set up on 
Linux as 'Remote Unix (lpd) queue', Remote Host is IP Address, Remote 
Queue is Raw.  These printers also exist on the NT side.  I actually set 
them up there first, to use the software with the printservers/network 
cards to assign the IP address to the devices.  Then I create them on 
Linux.

Comment 1 Crutcher Dunnavant 2000-10-11 15:15:35 UTC
Please move all further discusion of this bug to: Bug #11740

*** This bug has been marked as a duplicate of 11740 ***


Note You need to log in before you can comment on or make changes to this bug.