From owner-freebsd-questions Tue Jul 30 18:06:08 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22076 for questions-outgoing; Tue, 30 Jul 1996 18:06:08 -0700 (PDT) Received: from synwork.com (root@synwork.com [199.3.234.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA22068 for ; Tue, 30 Jul 1996 18:06:05 -0700 (PDT) Received: from synwork.com (flaq@ns1.synwork.com [204.120.255.17]) by synwork.com (8.6.12/8.6.12) with SMTP id UAA07559; Tue, 30 Jul 1996 20:05:50 -0500 Date: Tue, 30 Jul 1996 20:05:50 -0500 (CDT) From: Mike To: Steve Gibson cc: David Greenman , questions@FreeBSD.ORG Subject: Re: ls -l problem In-Reply-To: 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 Wed, 31 Jul 1996, Steve Gibson wrote: > 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... > > > --- That's all a problem needs to see is that it has been submitted to questions@freebsd.org and it goes away! :) ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Syn-Work Media, Inc. | WWW Development & Hosting | Life Safety http://www.synwork.com | Systems Integration | CCTV mike@synwork.com | Voice/Data/Fiber | Access Control Flaq on IRC | Dukane Distributor | BICSI/RCDD ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~