Red Hat Bugzilla – Bug 253979
installer creates hostname but fails to give it default hosts mapping, causes complex problems elsewhere
Last modified: 2007-11-30 17:12:14 EST
Description of problem:
The fedora 7 installer creates a system hostname, but fails to make an entry for
it in the /etc/hosts file.
You might think so-what, but this actually causes nasty troubles with delays
starting gnome applications, and yet people have said that it isn't a gnome bug
Others on the fedora irc have seen the same issue.
Take a look at this ubuntu link to a problem whose symptom happens identically
on fedora 7: https://bugs.launchpad.net/ubuntu/+bug/94048
I believe that the fedora 7 installer should by default create an /etc/hosts
entry mapping the installer-assigned hostname to the localhost interface, as the
ubuntu report recommends and how LOTS of ubuntu people have solved the problem.
Version-Release number of selected component (if applicable):
The delay problem with gnome is intermittent
No binding of hostname to ip address in /etc/hosts from install
A sensible default for the hostname in /etc/hosts from install would be 127.0.0.1
Just the short hostname, right, not the FQDN? I seem to remember us doing this
at some point and then not. Might be my fault with all the network
configuration changes in anaconda.
Yes just the short host name:
[root@Vigor12 ~]# uname -n
[root@Vigor12 ~]# hostname
When I mapped it to the localhost interface in /etc/hosts the problems went away:
[root@Vigor12 ~]# grep Vigor12 /etc/hosts
127.0.0.1 localhost.localdomain localhost DesktopPROD desktopprod
Fixed in rawhide. Thanks.