Re: mc starts after 60 second delay (fwd)

On Fri, 15 Sep 2006, Lindy Mayfield wrote:

Thanks very much!  That cured it.

I had the line --
interfaces = lo, vmnet1

in my smb.conf file because I was testing some things with VMWare
Server.  What is interesting is that I have the same interfaces
directive in my smb.conf file on a Centos 4.1 system and mc has no
problems there.  Probably there is an updated library somewhere for
that issue.

No. Most likely on the other machine you have MC which does not
have samba code built-in.

On 9/15/06, Pavel Tsekov <ptsekov gmx net> wrote:
---------- Forwarded message ----------
Date: Fri, 15 Sep 2006 00:30:16 +0300
From: Lindy Mayfield
To: Pavel Tsekov
Subject: Re: mc starts after 60 second delay

Yes, as a matter of fact I've recently installed samba.

why?  What are you thinking?

This is Ubuntu but on another system I have Centos4.1 where I've also
installed samba and mc works fine there.

what about samba could be doing this?  how could I test it?  shut down samba?

MC has support for samba. If samba support is enabled, MC will
read the global samba configuration file at startup. Unfortunately
the samba code that MC uses is a bit outdated and doesn't know of
certain changes made to the directives in the samba configuration
file. The "interfaces" directive is the one that we are interested
in - now it allows network interface names  (like eth0, wlan0, etc),
but it didn't in the past. Not  knowing this the samba code in MC
tries to resolve the interface name as if it was a host name.

Now, if you computer is not connected to the internet and
the "interfaces" directive in your configuration file does
contain a network interface name then MC will hang. To
workaround the hang you could comment out the directive,
or change its value so that it will contain an ip/mask

I hope that helps.

Mc mailing list

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]