https://bugzilla.novell.com/show_bug.cgi?id=340498#c6
Mark Gordon changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Info Provider|peter@plord.co.uk |
Resolution| |INVALID
--- Comment #6 from Mark Gordon 2007-11-12 11:58:12 MST ---
That's because you have DHCLIENT_SET_HOSTNAME="yes". You might want to turn
that off.
WRITE_HOSTNAME_TO_HOSTS="yes" is taking the hostname from /etc/HOSTNAME and
writing it to /etc/hosts. It's responsible for the last line of /etc/hosts:
127.0.0.2 plordnote.internal plordnote
/etc/HOSTNAME (defined at install time) has:
plordnote.internal
So WRITE_HOSTNAME_TO_HOSTS is actually doing something. It seems the problem
lies in the fact that there isn't complete agreement between the DHCP server
and your machine over what your hostname should be. If you have control over
your DHCP server, you should be able to set it to recognize your MAC address
and give you a consistent name of your choosing.
As I see it, the reported problem is INVALID, as WRITE_HOSTNAME_TO_HOSTS does
do something, though perhaps it's not what you expected it to do. If your
network is reliable, you shouldn't need to write the hostname to /etc/hosts.
Conversely, if your network is so unreliable that you need to write your
hostname to /etc/hosts, perhaps you probably shouldn't be getting your hostname
from DHCP.
If you're saying that you want to be able to cache the hostname that is
provided by DHCP (which in the above case is little more than an abbreviated
IP address), that's another issue, but it seems like a real corner case.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.