https://bugzilla.novell.com/show_bug.cgi?id=440809
User gfarrell@netspeed.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=440809#c15
--- Comment #15 from Geoff Farrell
NM notices the change and updates /etc/hosts and calls hostname (which modifies /proc/sys/kernel/hostname).
That's not what I see in Beta5, and I've just checked RC1, and it's the same. For a start, NetworkManager does nothing with a hostname change when the network is restarted (rcnetwork restart). Even though /etc/HOSTNAME has changed, /etc/hosts and /proc/sys/kernel/hostname remain unchanged after a network restart. With a reboot, NetworkManager notices the change and sets /proc/sys/kernel/hostname (by the 'hostname' command), but it doesn't change /etc/hosts. Its 127.0.0.2 line retains the randomly allocated 'linux-0mh9.site linux-0mh9' setting. So the programs that rely on /etc/hosts to get the hostname will get the wrong one. Maybe my suggested 'change-hostname' script doesn't need to apply the 'hostname' command in it (however, I can't see any harm in doing that) but RC1 still shows that it needs changes applied to /etc/hosts and /etc/HOSTNAME for a complete treatment of the problem, as it stands. Also, the Release Notes would have to mention that a reboot is necessary following running of the script. I still think that something should be done about this; I don't think it's wise to leave it in this state. The attached file shows detailed steps showing hostname changes for RC1. -- 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.