| 1 |
Dave Crane posted <200512291248.34613.d@×××××.net>, excerpted below, on |
| 2 |
Thu, 29 Dec 2005 12:48:34 -0500: |
| 3 |
|
| 4 |
>> because net.lo is not usefull for a system that provides services. |
| 5 |
>> for example running a ssh server for net.lo is kinda silly :) |
| 6 |
> |
| 7 |
> Maybe we should all remove the localhost line from /etc/hosts if it's silly. |
| 8 |
> Maybe /etc/fstab should be /etc/conf.d/filesystems? |
| 9 |
> |
| 10 |
>> > I'm asking this because last week at home I couldn't run apache2 |
| 11 |
>> > because I didn't have an interface up but lo. But this is silly, |
| 12 |
>> > because I could still use apache2 locally! |
| 13 |
>> > Am I wrong? Is my system wrong? |
| 14 |
>> |
| 15 |
>> Your system is correct, if you don't care for this you can change the |
| 16 |
>> behaviour in /etc/conf.d/rc with the RC_NET_STRICT_CHECKING variable |
| 17 |
> |
| 18 |
> Or maybe its should be left to the app. adding RC_NET_STRICT_CHECKING would |
| 19 |
> have other consequences. One size does not fit all here. If net.lo is the |
| 20 |
> only thing that satisfies net on a given system and the process doesnt have a |
| 21 |
> problem attaching to that (as I just verified with both sshd and apache2), |
| 22 |
> then let it be. |
| 23 |
|
| 24 |
How do you figure? One size doesn't fit all, but you are asking that your |
| 25 |
size fits all? |
| 26 |
|
| 27 |
If you want lo to provide net, it can, set the variable accordingly (lo). |
| 28 |
If you want at least one other network up before net is considered up, |
| 29 |
great, that's possible too (set no). On a multi-homed host, if you want |
| 30 |
them all up before net is considered up, that too is possible, just set |
| 31 |
RC_NET_STRICT_CHECKING=yes. |
| 32 |
|
| 33 |
Other than that, we'd have to be deciding for each app, and I can assure |
| 34 |
you, making that happen by default is FAR more trouble than it's worth, |
| 35 |
when few need it and for those that do, the scripts are as easily modified |
| 36 |
for those few as they'd have to be for EVERYONE if there weren't the very |
| 37 |
sane RC_NET_STRICT_CHECKING variable there. |
| 38 |
|
| 39 |
As for discovering the variable, it's the job of a sysadmin, which in |
| 40 |
effect everyone choosing to run Gentoo on their system is, to be familiar |
| 41 |
with at least the basic settings on their installation. This is one such |
| 42 |
basic setting, in a very general location, too, not hidden away, |
| 43 |
impossible to find. Being expected to be aware of such basic settings |
| 44 |
just comes with the territory. |
| 45 |
|
| 46 |
-- |
| 47 |
Duncan - List replies preferred. No HTML msgs. |
| 48 |
"Every nonfree program has a lord, a master -- |
| 49 |
and if you use the program, he is your master." Richard Stallman in |
| 50 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-amd64@g.o mailing list |
Archives