On Sat, 7 Feb 2004 [EMAIL PROTECTED] wrote: > > > > > > I have been experiencing a noticable ( > 3 seconds) delay when I > > > > > > print a job to a printers connected to terminals. The queues are defined > > > > > > as jetdirect and the spooler uses same mechanism for terminal connected > > > > > > and network connected printers. Network connected printers get data right > > > > > > away, terminal connected get it after more than 3 seconds passes. What > > > > > > gives, how can I change it? I like the immediacy of good systems, this > > > > > > just doesn't feel right, and the users are grumbling too. julius > > > > > > > > > > > > p.s. i tested it with a printer connected to a terminal - delay, same > > > > > > printer connected to external hp jetdirect box - no delay. > > > > > > > > > > I can't remember the fix! but it is a network problem, and I think it was > > > > > reverse DNS not correct, but it is a network problem. Use tethereal and > > > > > look at the data to see what it's waiting for > > > > > > > > > James, > > > > I'll check it out tomorrow, but for the record, both the hardware > > > > jetdirect and workstations have entries in /etc/hosts file and are set by > > > > dhcpd. ping to the workstation and telnet to "wsaddr 9100" are immediate, > > > > just the printing start is delayed. julius > > > > > > Still trying to recall: it might be as simple as > > > wsXXX not listed in /etc/hosts on the SERVER > > > > > > If this is done then use tethereal, but the delay is NOT on the ws ie data > > > to port 9100 to printer is instant, delay is on the server spooler > > > while it fiddles with network addresses > > > > > James, > > nice try, no cigar. We are talking about the same spooler being > > fast with jetdirect box and slow with jetdirect queue. The workstation / > > printer address most certainly is in the /etc/hosts. julius > > The jetdirect box and the jetdirect queue are different machines. > So the spooler is fast to one and slow to one! So What ? > > The spooler speed is due to 'name lookups' and 'localhost'. Try tethereal!
James, uhh ... no. This is not the name lookup. You missed my little summary. The problem is in a particular program used in the wonderful chain of hope we call unspooler. The program in question, hpnpf, is fired up ob my business system. It talks to the Jetdirect devices and asks them "What kind of HP equipment are you?" question. Hardware JetDirect replies immediately and printing starts right away. Non-HP devices, like LTSP terminal queues don't have a good answer, so there is this time spent waiting for response that introduces delay. The problem is *not* on the Linux / LTSP side at all. julius ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
