Date: Fri, 25 Jun 2004 11:39:38 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: danny@cs.huji.ac.il Cc: tjr@FreeBSD.org Subject: Re: waiting on sbwait Message-ID: <200406251839.i5PIdcTV060752@gw.catspoiler.org> In-Reply-To: <20040624124311.22B0643D62@mx1.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406251839.i5PIdcTV060752>