[cups.bugs] [HIGH] STR #1821: cups-lpd oddities with printer-state attribute
harry
harry at schmalzbauer.de
Fri Jul 7 21:04:38 PDT 2006
[STR New]
I use cups-lpd (1.2.1) on FreeBSD 6.1-stable via inetd (tcp6 but that
doesn't matter)
My printcap simply references the loaclhost remote queue:
lp|HL-5150D|1200dpi Duplex-Laser monochrom:rm=localhost:rp=HL-5150D:
'lpq' returns that printer is not ready although printing is working well
and cups-lpd logs the following:
Jul 4 18:44:27 tek cups-lpd[1024]: Connection from localhost
(IPv6 ::1)
Jul 4 18:44:27 tek cups-lpd[1024]: Send queue state (short) for
HL-5150D
Jul 4 18:44:27 tek cups-lpd[1024]: No printer-state attribute
found in response from server!
Jul 4 18:44:27 tek cups-lpd[1024]: Closing connection
Now the really wiered:
When I change :rm=localhost: to :rm=tek: (the machine name which resolves
to fec0::1:0:0:2:3) lpq is working as expected.
No change if I use v4 addresses instead.
Only working scenario is from localhost to tek.
Any other machine contacting tek also gets the wrong status and cups-lpd
logs the same "No printer-state attribute" message.
Here's the relevant line in inetd.conf:
printer stream tcp6 nowait daemon
/usr/local/libexec/cups/daemon/cups-lpd cups-lpd
Attached is my cupsd.conf in a very relaxed configuration for testing
purposes.
Link: http://www.cups.org/str.php?L1821
Version: 1.2.1
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cupsd.conf
URL: <https://lists.cups.org/pipermail/cups/attachments/20060708/6cbc9497/attachment.ksh>
More information about the cups
mailing list