From owner-freebsd-hackers Sun Dec 1 14:56:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA04485 for hackers-outgoing; Sun, 1 Dec 1996 14:56:36 -0800 (PST) Received: from terra.stack.nl (terra.stack.nl [131.155.140.128]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA04480 for ; Sun, 1 Dec 1996 14:56:34 -0800 (PST) Received: from xaa.stack.nl (uucp@localhost) by terra.stack.nl (8.8.3) with UUCP id XAA08481; Sun, 1 Dec 1996 23:52:46 +0100 (MET) Received: (from freebsd@localhost) by xaa.stack.nl (8.8.3/8.8.2) id XAA00529; Sun, 1 Dec 1996 23:18:53 +0100 (MET) Message-ID: Date: Sun, 1 Dec 1996 23:18:53 +0100 From: freebsd@xaa.stack.nl ("FreeBSD matters of Mark Huizer (xaa)") To: ache@nagual.ru (?????????????) Cc: StevenR362@aol.com, kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org Subject: Re: cvsup can't find host - sometimes References: <961201123255_1751372447@emout01.mail.aol.com> <199612011926.WAA00759@nagual.ru> X-Mailer: Mutt 0.53-export Mime-Version: 1.0 In-Reply-To: <199612011926.WAA00759@nagual.ru>; from ????????????? on Dec 1, 1996 22:26:07 +0300 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > (this is from a cvsup -L 2 cvsupfile | mail I send to myself when cvsup > > > is finished) > > > > > > Pinging freefall works fine. I'm just wondering whether this is a > > > network problem (load, nameservers unreachable or some such) or > > > if it might be a cvsup problem since the lookup is done by the > > > program and the name search might be not 'hard enough'. > > > > > I get this also on a 14.4 dialup connection while doing a couple of > > simultaneous ftp's. It seems to be the result of a slow/overloaded link > > and a timeout. > > I saw it too without any overload on my 28.8K dialup connection. > It not only freefall.cdrom.com but cvsup.nl.freebsd.org too. > Perhaps we could check that out from both sides :-) Perhaps if I put the logfile of cvsup.nl.freebsd.org next to your dialin behaviour, I can check if I can come up with something. Does this also happen (something worth testing) with the 'real' hostname alterego.stack.nl? Perhaps some nameserver is taking a little time or something (perhaps even the machine was just down :-) Mark Huizer (xaa@stack.nl)