Till
Buchan Milne wrote:
Till Kamppeter wrote:
[EMAIL PROTECTED] wrote:
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.
See "Setting of name for 'localhost' is malfunctioning" and "Pathetic that box is to be named 'localhost' when using DNS" threads in cooker.
Someone needs to take action, and advice from the community, on this for 10 IMHO. I have to remember to use the advanced button twice in drakconnect to get the behaviour I want (the default in Windows), and enter the same hostname 3 times (instead of just once like in Windows).
Regards, Buchan
-- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
***************************************************************** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *****************************************************************
