X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Thorsten Kampe Subject: Re: [ANNOUNCEMENT] Updated:lftp-3.5.9-1 Date: Tue, 13 Feb 2007 09:10:13 -0000 Lines: 19 Message-ID: References: <2n01t2d0tjsju80t9h5uaa9r8tv5u2popm@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.70.2067 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com * Andrew Schulman (Mon, 12 Feb 2007 10:12:54 -0500) > > > lftp ftp.microsoft.com > > lftp: host name resolve timeout > > I'm not able to reproduce this problem: I figured it out myself: it's the "dns:fatal-timeout 0" setting in my .lftprc. The funny thing is that "0" is the default and actually means "no timeout" man lftp "dns:fatal-timeout (seconds) limit the time for DNS queries. If DNS server is unavailable too long, lftp will fail to resolve a given host name. 0 means unlimited, the default." It's a classical bug, my Linux lftp 3.5.7 shows the same behaviour. Thorsten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/