On a wide range of boxes, I have strange entries appearing in /etc/hosts. I would expect that this is caused by something funny that Portage is doing, but I can't find any details. Entries are: on a bunch of boxes 10.10.10.1 pitr-int 10.10.10.2 dustpuppy-int 10.10.10.3 poseidon-int 134.68.220.30 toucan and on a different box: 192.168.0.2 gravity.twi-31o2.org gravity the first bunch of boxes are on two completely unrelated networks, neither of which is in the 10./8 network; the second is in a 172.16.1/24 subnet. I understand that toucan is the Gentoo mail server, but why's it in /etc/hosts? Google returns very little, other than a tangential reference to FTP by someone who is otherwise fairly confused. It looks like these are harmless, but what are they and can I delete them?
Are you using dhcpcd and ntp by any chance?
Yes -- how does that relate?
dhcpcd will automatically add entries to hosts if you don't tell it not to. You need to use something like: dhcpcd_eth0="-N" in /etc/conf.d/net in order to tell it not to.
Just delete them, leftover from building stages. :) wolf31o2 could give you more info, maybe :)
As a feature for building stages/livecds, catalyst pulls in the build system's /etc/hosts file. This allows for using things like local mirrors and such on a network that might not have DNS. Anyway, this is supposed to be replaced with the backup copy that catalyst makes, hosts.bck, but there was a bug in catalyst that caused this to not happen. As such, it kept the host entries from the build machines in the tarballs. This has since been fixed, and really was a cosmetic problem, anyway.
Great, thanks, and hopefully other concerned users will find this bug entry! :)
*** Bug 182330 has been marked as a duplicate of this bug. ***
Chris, you did it again? :P
No, I did not. No user using the 2007.0 stages would have gcc 3.4.6 installed. The user in question upgraded, and probably just noticed this. The bug was fixed in catalyst a long time ago.
