From owner-freebsd-hackers@FreeBSD.ORG  Fri Jun 25 18:40:33 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0C5E916A4CE; Fri, 25 Jun 2004 18:40:33 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4755243D54; Fri, 25 Jun 2004 18:40:32 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i5PIdcTV060752;
	Fri, 25 Jun 2004 11:39:42 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200406251839.i5PIdcTV060752@gw.catspoiler.org>
Date: Fri, 25 Jun 2004 11:39:38 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: danny@cs.huji.ac.il
In-Reply-To: <20040624124311.22B0643D62@mx1.FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: mpf@inodes.us
cc: freebsd-hackers@FreeBSD.org
cc: tjr@FreeBSD.org
Subject: Re: waiting on sbwait
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2004 18:40:33 -0000

On 24 Jun, Danny Braniss wrote:

> found the cause: NFS/amd
> a user had several symlinks to /net/host/xyz, and host was down.
> doing ls -F /net/host/xyz does the trick, the machine becomes
> unresponsive.

/net is evil.  A fun trick is to attempt to access
/net/nonexistenthost and watch amd wedge while it gropes around the DNS
tree looking for nonexistenthost.  At a previous job I stumbled across
this when I noticed that amd would hang whenever we lost our internet
connection.  Watching DNS queries sent to the Internet revealed all
sorts of interesting things that could be considered to be a leak of
sensitive information.

I also don't like NFS exporting /, and accessing /net/machine doesn't
work too well if / isn't exported.