From owner-freebsd-stable@FreeBSD.ORG Sun Nov 18 19:42:44 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E846816A46D for ; Sun, 18 Nov 2007 19:42:43 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 3B22B13C45B for ; Sun, 18 Nov 2007 19:42:42 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id lAIJgIEO066083; Mon, 19 Nov 2007 02:42:18 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id lAIJgIfw066082; Mon, 19 Nov 2007 02:42:18 +0700 (KRAT) (envelope-from eugen) Date: Mon, 19 Nov 2007 02:42:17 +0700 From: Eugene Grosbein To: Torfinn Ingolfsen Message-ID: <20071118194217.GA65999@svzserv.kemerovo.su> References: <20071118194104.9f7273dc.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071118194104.9f7273dc.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD.org acting up again? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2007 19:42:45 -0000 On Sun, Nov 18, 2007 at 07:41:04PM +0100, Torfinn Ingolfsen wrote: > Is the freebsd.org machine acting up again? > I get connection resets when I try to do > root@kg-work# fetch http://www.FreeBSD.org/ports/INDEX-6.bz2 > fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Connection reset by peer > > (or 'make fetchindex' or 'http://www.freebsd.org/') > Or is this something else? The same here: port 80 refuses connections. Eugene Grosbein