> because net.lo is not usefull for a system that provides services. > for example running a ssh server for net.lo is kinda silly :)
Maybe we should all remove the localhost line from /etc/hosts if it's silly. Maybe /etc/fstab should be /etc/conf.d/filesystems? > > I'm asking this because last week at home I couldn't run apache2 > > because I didn't have an interface up but lo. But this is silly, > > because I could still use apache2 locally! > > Am I wrong? Is my system wrong? > > Your system is correct, if you don't care for this you can change the > behaviour in /etc/conf.d/rc with the RC_NET_STRICT_CHECKING variable Or maybe its should be left to the app. adding RC_NET_STRICT_CHECKING would have other consequences. One size does not fit all here. If net.lo is the only thing that satisfies net on a given system and the process doesnt have a problem attaching to that (as I just verified with both sshd and apache2), then let it be. What if you have apache setup SPECIFICALLY to attach to 127.0.0.1 so as to not be publicly accessible? I've done this numerous times in the past for various reasons. If it fails at init, it would be logical to check the logfile for the app and you'd quickly know what was wrong instead of having to mail a list. Sorry to go off on this, but things have been changing in the last few months in ways illogical to me. I've been running gentoo since pre 1.0 days and this has greatly concerned me lately. Every distro has it's quirks and funny ways of doing things, but the list seems to be growing with gentoo for no good reason. -- Dave Crane -- [email protected] mailing list
