On Fri 19 Jul 2013 at 10:34:45 +0200, Hagen Fuchs wrote: > Is there a way to debug the communication between avahi-daemon and cupsd > that doesn't involve an actual debugger? I found avahi-daemon's > '--debug' switch to be not that verbose. Not that I can think of immediately. However, I can reproduce your experience with ServerName on Wheezy and Sid. With debug logging on cups was restarted. Both error_logs are attached. On Wheezy: D [19/Jul/2013:15:37:27 +0100] Added auto ServerAlias example.com I [19/Jul/2013:15:37:27 +0100] Loaded configuration file "/etc/cups/cupsd.conf" Later in the log: I [19/Jul/2013:15:37:27 +0100] Resuming new connection processing... D [19/Jul/2013:15:37:27 +0100] Avahi client started D [19/Jul/2013:15:37:27 +0100] Registering Avahi printer HP_LaserJet_1018 with name "HP_LaserJet_1018 @ example.com" and type "_ipp._tcp,_cups,_universal" D [19/Jul/2013:15:37:27 +0100] Adding TXT record for HP_LaserJet_1018 @ example.com (_ipp._tcp) D [19/Jul/2013:15:37:27 +0100] Adding TXT record for HP_LaserJet_1018 @ example.com (_cups._sub._ipp._tcp) D [19/Jul/2013:15:37:27 +0100] Adding TXT record for HP_LaserJet_1018 @ example.com (_universal._sub._ipp._tcp) D [19/Jul/2013:15:37:29 +0100] Avahi entry group established for HP_LaserJet_1018 @ example.com So cups knows what its ServerName is and avahi gets to use it. On Sid: D [19/Jul/2013:15:52:12 +0100] Added auto ServerAlias example.com I [19/Jul/2013:15:52:12 +0100] Loaded configuration file "/etc/cups/cupsd.conf" Then later: I [19/Jul/2013:15:52:12 +0100] Resuming new connection processing... D [19/Jul/2013:15:52:12 +0100] cupsdRegisterPrinter(p=0x7fa497621e50(2200)) D [19/Jul/2013:15:52:12 +0100] Registering "2200 @ amd64-cups-unstable" with DNS-SD type "_printer._tcp". D [19/Jul/2013:15:52:12 +0100] Registering "2200 @ amd64-cups-unstable" with DNS-SD type "_ipps._tcp". D [19/Jul/2013:15:52:12 +0100] DNS_SD "2200 @ amd64-cups-unstable" printer-type=0x809046 D [19/Jul/2013:15:52:12 +0100] DNS_SD "2200 @ amd64-cups-unstable" printer-state=3 D [19/Jul/2013:15:52:12 +0100] DNS_SD "2200 @ amd64-cups-unstable" Copies=T Again, cups knows what its ServerName is but it is not used when a queue is registered. I don't know whether this change in behaviour is intentional but wonder whether asking upstream is worthwhile. Odyx? Regards, Brian.
Attachment:
servername-wheezy.gz
Description: Binary data
Attachment:
servername-sid.gz
Description: Binary data