From owner-freebsd-current Fri Jun 26 23:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22508 for freebsd-current-outgoing; Fri, 26 Jun 1998 23:39:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22501 for ; Fri, 26 Jun 1998 23:39:04 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA28921; Fri, 26 Jun 1998 23:39:14 -0700 (PDT) Message-Id: <199806270639.XAA28921@implode.root.com> To: Joel Ray Holveck cc: gt@freebsd.first.gmd.de, freebsd-current@FreeBSD.ORG Subject: Re: /dev/io In-reply-to: Your message of "Sat, 27 Jun 1998 00:21:02 CDT." <199806270521.AAA01028@detlev.UUCP> From: David Greenman Reply-To: dg@root.com Date: Fri, 26 Jun 1998 23:39:14 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> BTW. FreeBSD.ORG is not reachable from 160.45.2.xxx. Who is the >> person I could ask about this problem? > >Find the outage. RTFM: traceroute(8). It's usually going to be your >local network, so try your local admin. If it's not, then wait a >little while; TCP/IP is designed to be self-healing, so many problems >will sort themselves out in a short time (could be two minutes). Some >problems require human intervention, and may take all day. If it is >not your LAN, then talk to your upstream. They can usually sort >things out. Actually, it was an error in CRL's IGP and required a NOC person to fix it. I called them earlier today and the problem was resolved in less than an hour. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message