"midnight commander" needs nameserver - why?
Helmut Hullen
some time ago I had complained that the new "midnight commander" needs
more than 10 seconds to start.
Now I have found the direct obstacle:
On my major linux machine I run a local nameserver (dnsmasq or ISC-
bind). If I stop this nameserver then mc starts immediately, not after
doing some strange things in the background within the first 10 seconds.
For what reason employs the "midnight commander" a (local) nameserver?
Is that a general problem of the new "midnight commander" or only a
special problem of the slackware packet?
Viele Gruesse
Helmut
"Ubuntu" - an African word, meaning "Slackware is too hard for me".
Dave Dickman
How is dnsmasq configured? If it doesn't use /etc/hosts, does its
configuration match the contents of that file? Have you used the localhost
entry as a placeholder for anything else? (i.e. - does 127.0.0.1 have more
than just localhost as a name?) What options are enabled? How is nsswitch
set? Are you using a bogus resolv.conf?
Sorry I have more questions than answers, but I have used dnsmasq, and there
are many things that affect it, and circular references are easy to create.
Did you try running dnsmasq in debug mode to see what the requests are?
--
Linux User #152843