On 09/10/11 09:19, Tim Allen wrote:
Doing some more investigation into
HostNameLookups On
in /etc/cups/cupsd.conf (this line was not present on either machine)
Setting HostNameLookups On on both machines gives
printer1@helix
At some point the default setting of this must have changed in cups, as
I haven't modified cupsd.conf for a couple of years.
While experimenting (enabling this on one machine or another but not
both), I got some really strange effects, sometimes getting a single
remote printer listed multiple time in variations of
[email protected]
printer1@helix
[email protected]
I was thrown a bit in that something is caching the cups web page, so
making a change to cupsd.conf can take around 10 minutes to have an
effect (it seemed logical that it should only be necessary on the local
machine).
Now I know this, I still need to fully explore the effects of
BrowseShortNames No
in various permutations on each machine!
Conclusion is:
Helix print queues are reported by fleet as [email protected] rather
than printer@helix as on Lenny and Etch. This is likely due to a change
in the default behaviour of HostNameLookup in /etc/cups/cupsd.conf.
By enabling HostNameLookup on fleet but keeping it disabled on helix, we
get helix queues reported with FQDN's ([email protected]). By
enabling HostNameLookup on both machines, we get helix queues reports
with just the hostname (as in earlier releases) (printer@helix).
Relevant sections of cupsd.conf
(helix is a remote cups server we want to access from fleet):
Fleet:
# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
BrowseAllow @LOCAL
BrowsePoll helix.domain.co.uk
# By not enabling host name lookups, helix printers are reported with fqdn
#HostNameLookups On
# Don't truncate non-duplicated names on helix
#BrowseShortNames No
Helix:
# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseLocalProtocols CUPS dnssd
# Resolve hostname for fleet
HostNameLookups On
# Don't truncate non-duplicated names
#BrowseShortNames No
--
Next meeting: Bournemouth, Tuesday 2011-11-01 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
How to Report Bugs Effectively: http://goo.gl/4Xue
