From owner-freebsd-questions  Tue Jul 30 01:26:54 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA29185
          for questions-outgoing; Tue, 30 Jul 1996 01:26:54 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA29179
          for <questions@FreeBSD.ORG>; Tue, 30 Jul 1996 01:26:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id BAA28542; Tue, 30 Jul 1996 01:26:27 -0700 (PDT)
Message-Id: <199607300826.BAA28542@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Steve Gibson <steve@aries.interspace.com.au>
cc: questions@FreeBSD.ORG
Subject: Re: ls -l problem 
In-reply-to: Your message of "Tue, 30 Jul 1996 17:33:50 +1000."
             <Pine.LNX.3.91.960730173004.4803A-100000@aries.interspace.com.au> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 30 Jul 1996 01:26:27 -0700
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I have a problem in that when in the root directory, if I issue an ls -l
>the process locks up. It won't be killed, even with a -9. Any parameter 
>other than -l works without a problem, and I can use -l in any other 
>directory.
>
>Any ideas as to what might be going on?

   Sounds like a stuck NFS mount - possible caused by the server being down.

-DG

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