From owner-freebsd-current  Wed Aug  7 04:59:10 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA08940
          for current-outgoing; Wed, 7 Aug 1996 04:59:10 -0700 (PDT)
Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA08931
          for <freebsd-current@freebsd.org>; Wed, 7 Aug 1996 04:59:04 -0700 (PDT)
Received: (from news@localhost) by haywire.DIALix.COM (8.7.5/8.7.3) id TAA27507 for freebsd-current@freebsd.org; Wed, 7 Aug 1996 19:58:59 +0800 (WST)
Received: from GATEWAY by haywire.DIALix.COM with netnews
	for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com)
To: freebsd-current@freebsd.org
Date: 7 Aug 1996 11:58:58 GMT
From: peter@spinner.DIALix.COM (Peter Wemm)
Message-ID: <4ua0e2$p3n$1@haywire.DIALix.COM>
Organization: DIALix Services, Perth, Australia.
References: <199608040322.MAA06694@genesis.atrad.adelaide.edu.au>
Subject: Re: problem with -current system grinding to a halt...
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <199608040744.AAA13305@root.com>,
	dg@Root.COM (David Greenman) writes:
> 
>    This can happen if your nameserver isn't reachable. Have you tried "w -n" ?
> This disables the nameserver lookups and is useful for this specific problem.
> 
> -DG

Not any more.. Now it causes an extra DNS lookup if the ut_host field
isn't a numeric IP address... :-(  Sigh.

-Peter

> David Greenman
> Core-team/Principal Architect, The FreeBSD Project