Unable to start midnight commander under Ubuntu. It's a server, where I was using it for a lont time always. Today I logged in and found mc
hangs on start.
dims@sagittarius-a:~$ mc
and nothing happens.
Reinstall didn't help.
Removing config
rm -rf .config/mc
didn't help.
Removing global config
sudo rm /etc/mc
and reinstall causes
dims@sagittarius-a:/etc$ mc
sfs_init(): Warning: file /etc/mc/sfs.ini not found
i.e. didn't help and config files didn't restored dusring install by some reason.
What else can be tried?
UPDATE
Wow! It just loads long! No less than 60-100 seconds. It appeared while I was writing this. So the question persists: what does it do so long? Calculating mass of proton? How to wean it from this habit?
UPDATE 2
Reinstalling MC doesn't help.
UPDATE 3
Recently I configured my globally the domain name, which I am using as default in my LAN
. Now, the commands like
dims@sagittarius-a:~$ host anything
anything.MYDOMAIN is an alias for MYDOMAIN.
MYDOMAIN has address GLOBAL_IP_OF_MY_SITE_1
MYDOMAIN has address GLOBAL_IP_OF_MY_SITE_2
I read, that MC does some DNS lookup on startup and it can slow the process. I would like to understand, what is happening to make my own correct configuration, because answers in that question are incomplete.