-=-=-=- Name : cups Relocations: (not relocateable) Version : 1.1.19 Vendor: MandrakeSoft Release : 10mdk Build Date: Thu 18 Sep 2003 04:24:28 AM CEST Install Date: (not installed) Build Host: no.mandrakesoft.com Group : System/Servers Source RPM: (none) Size : 3791412 License: GPL Signature : (none) Packager : Till Kamppeter <[EMAIL PROTECTED]> URL : http://www.cups.org Summary : Common Unix Printing System - Server package Description :
-=-=-=- Till Kamppeter <[EMAIL PROTECTED]> 1.1.19-10mdk
- Fixed bug 5615 by means of the following two changes: o Make the CUPS daemon not sending broadcast packages with the host name "localhost". In this case the IP address of the appropriate interface is used (patch 22). o Do not insert "ServerName" directives in /etc/cups/cupsd.conf any more during the startup of CUPS (with the /usr/sbin/correctcupsconfig script).
Hmm, it seems cups admits defeat to drakconnect ...
IMHO, drakconnect's job is to ensure: 1)The hostname is never set to localhost if there is any networking device attached to the machine in question 2)Reverse lookups will always work. In the case of DHCP, drakconnect should ensure that the hostname is sent as DHCP_HOSTNAME (in which case we hope the DHCP administrator has working DDNS), and doesn't touch tmdns.conf. In the case of no DHCP, tmdns.conf is not touched (and we hope the other machines have working tmdns).
I didn�t know that this was a long-standing in drakconnect (or even in the former draknet). Otherwise I had perhaps tried to press the drakconnect guys to fix it (posting bug with "blocker" priority and more ...). I thought it was a fault of CUPS and so I fixed CUPS. In addition, this fix also works when one uses other network config tools or does a faulty configuration manually. This makes CUPS in our default configuration more or less "idiot-proof". But in general, it is better to fix the bugs at their origins instead of making workarounds.
Till
