From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 3 12:28:39 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1D4416A4CE for ; Thu, 3 Feb 2005 12:28:39 +0000 (GMT) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98B1B43D58 for ; Thu, 3 Feb 2005 12:28:36 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: (qmail 4345 invoked from network); 3 Feb 2005 12:28:34 -0000 Received: from apircalabu.dsd.ro (10.10.15.22) by mail.dsd.ro with AES256-SHA encrypted SMTP; 3 Feb 2005 12:28:34 -0000 Date: Thu, 3 Feb 2005 14:31:27 +0200 From: Adi Pircalabu To: Aleksander Rozman - Andy Message-ID: <20050203143127.0b435416@apircalabu.dsd.ro> In-Reply-To: <6.0.0.22.2.20050203003439.05105e70@pop3.triera.net> References: <6.0.0.22.2.20050203003439.05105e70@pop3.triera.net> Organization: BitDefender X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; i386-portbld-freebsd4.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BitDefender-SpamStamp: 1.1.3 044000040111AAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQ X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.1 on mail.bitdefender.com X-BitDefender-Spam: No (13) cc: freebsd-hackers@freebsd.org Subject: Re: Weird problem with midnight commander (Freebsd 5.3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 12:28:39 -0000 On Thu, 03 Feb 2005 00:34:50 +0100 Aleksander Rozman - Andy wrote: > I am having weird problem. I have installed FreeBSD 5.3 on several > machines, and on two of those machines midnight commander has serious > problems. When I run it, it needs a long time to start, and I mean > long, about 5 minutes or so. Did anybody have a same problem? How did > you fix it. Oh one of those machines was fresh install, and other was > update... I had the same problem, and fixed it by setting up the right pair IP/hostname in /etc/hosts. So, as Dimitry said it's most of a resolver issue. -- Adrian Pircalabu Public KeyID = 0x04329F5E -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/