[12.06.2013 20:34] [Carlos E. R.]:
YaST should not add that entry to the hosts file;
Or it should make sure it also adds 127.0.0.2 to 'lo'. Which is what used to happen. If that doesn't happen anymore, that is the real problem.
All those fine details escape my capabilities :-)
As I just said in bugzilla:
What I would propose is a compromise: as there is a tick box to enable/disable this in YaST network configuration module, that tick box should display a text explaining what it does, and what breaks either way, so that if we get hit by the problems we know where they come from and we don't need to google it ;-)
There is a tickbox in YaST configuration as Per mentioned in the first response in this thread, Message-ID: <kp3ug9$sdf$1@saturn.local.net>. In many installation instructions (for example, if you install a SAP system on SLES), you get a direct hint to make sure this box is not ticked. Once you learn that ticking this box writes 127.0.0.2 with your hostname into /etc/hosts, you know that you don't want this feature. AFAIK, the box was unchecked the last times I installed openSUSE (and SLES). At some time, it added 127.0.0.2 to /etc/sysconfig/network/ifcfg-lo too - and this was needed because of some strange rules in CUPS access lists ("allow 127.0.0.2") that were introduced for some obscure reasons. When you look at postfix' config with the line "inet_interfaces = $myhostname, localhost", it is sure meant that $myhostname is resolved to an "outside" address (as opposed to a localhost address). Postfix should check that the given addresses are available for its local installation, though. Maybe one can tell Wietse that this is a security flaw, it will be fixed at once ;-) Just my 2¢, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org