Am Mon, 29 Dec 2008 14:44:15 +0300 schrieb Sergej Pupykin :

It is bug-feature I think. As I understand it is dns resolving problem. mc try to resolve local ips. You may put it into /etc/hosts

127.0.0.1 localhost.localdomain localhost 192.168.1.2 myhostname

Yeah, i always saw this on unusual installed DNS environments. Mostly the time when the machine hostname could not be solved by local DNS, either from an real DNS-Server or via /etc/hosts. So for dhcp-based IP-setting (and the crappy router/box don't resolve the hostname when the lease is provided) i would assume to put the hostname as an alias on the localhost line in /etc/hosts. Ideally there would be a command line parameter to disable all network related checking for mc... Gerhard

On Mon, Dec 29, 2008 at 11:25 PM, Baho Utot wrote:

On Monday 29 December 2008 06:44:15 am Sergej Pupykin wrote:

...

It is bug-feature I think. As I understand it is dns resolving problem. mc try to resolve local ips. You may put it into /etc/hosts

127.0.0.1 localhost.localdomain localhost 192.168.1.2 myhostname

This would be better:

127.0.0.1 localhost.localdomain localhost 127.0.0.2 myhostname.mydomain myhostname

Works in a dhcp environment :)

...

-------- Original Message -------- Subject: [arch-general] Slow startup of mc From: Abdul Halim To: arch-general@archlinux.org Date: Mon Dec 29 2008 14:38:04 GMT+0300 (MSK)

...

Hi. I just found out that mc (midnight commander) in extra repository is buggy in a sense that it will take around 7 secs or more to start. This happens to me on several machines. Other distro are reporting this issues too: https://savannah.gnu.org/bugs/?24038

To resolve this issue, I have downloaded mc-mp from community which is more stable.

I am suggesting that mc to be removed from the extra repo since it is an unstable version of mc.

Regards.

archlinuxsagi

Thanks for tip. Both solutions work. I guess mc is no longer buggy then. :-)