On Fri, 6 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
-------------------------------------------------------
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
