On Thu, 2008-01-10 at 00:46 +0100, Lennart Poettering wrote:
On Wed, 09.01.08 17:36, G.Wolfe Woodbury (ggw(a)wolves.durham.nc.us)
wrote:
> >> What happens in practice, though, is that things that expect network
> >> services to be running will do DNS lookups, hanging for minutes at at
> >> time when there is no response.
> >
> > Looks like a good way to identify bugs to me... the DNS hang needs
> > fixed, not worked around.
>
> One major help would be for Fedora to _not_ mangle the localhost line in
> /etc/hosts. This has casued me several headaches until I learned to
> remove the local realname from the default localhost line.
>
> Sure, its not technically incorrect, but its not nice when you've got
> static addresses on a LAN.
Although this is totally off-topic: I still think the proper fix is
something like this:
http://0pointer.de/lennart/projects/nss-myhostname/
http://0pointer.de/lennart/projects/nss-myhostname/README.txt
I wrote that a while back. Maybe someone wants to dust this off and
get it into Fedora and activated by default?
This saved me a couple of times on embedded boxes, where each of the
devices used a different hostname and I had to guarantee that the
hostname stayed resolvable in all cases, with a ro root directory.
This seems like a nice idea - actually even better idea would be to be
able to pass some arguments to modules in nsswitch.conf and then simply
put:
hosts: files dns files(conf=/etc/hosts-fallback)
The first files module would look into the regular /etc/hosts and the
second one into the /etc/hosts-fallback.
But since there is no (<parameters>) syntax in nsswitch.conf currently,
and the modules are not parametrized, your special module would work
too. Also your proposed module has an advantage that it doesn't have to
be configured in any way.
So what about including this module in Fedora?
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb