From owner-freebsd-questions Tue Jul 30 16:35:59 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA17421 for questions-outgoing; Tue, 30 Jul 1996 16:35:59 -0700 (PDT) Received: from aries.interspace.com.au (steve@aries.interspace.com.au [203.22.192.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17416 for ; Tue, 30 Jul 1996 16:35:55 -0700 (PDT) Received: (from steve@localhost) by aries.interspace.com.au (8.7.5/8.6.9) id JAA06275; Wed, 31 Jul 1996 09:35:34 +1000 Date: Wed, 31 Jul 1996 09:35:33 +1000 (GMT+1000) From: Steve Gibson To: David Greenman cc: questions@FreeBSD.ORG Subject: Re: ls -l problem In-Reply-To: <199607300826.BAA28542@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, David Greenman wrote: > >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. Well, the FreeBSD box is our network server, and doesn't mount anything from any other server. However, the problem seems to have gone away over night... Thanks to those who responded... --- Interspace Australia Pty Ltd Steve Gibson - System Administrator