From owner-freebsd-hackers  Thu Apr 13 17:23:03 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id RAA02826
          for hackers-outgoing; Thu, 13 Apr 1995 17:23:03 -0700
Received: from ain.charm.net (ain.charm.net [198.69.35.206])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA02820
          ; Thu, 13 Apr 1995 17:22:59 -0700
Received: (from nc@localhost) by ain.charm.net (8.6.11/8.6.9) id UAA07627; Thu, 13 Apr 1995 20:16:59 -0400
Date: Thu, 13 Apr 1995 20:16:59 -0400 (EDT)
From: Network Coordinator <nc@ain.charm.net>
To: freebsd-hackers@FreeBSD.org, freebsd-questions@FreeBSD.org
Subject: Proceses that won't die - follow up
Message-ID: <Pine.BSF.3.91.950413201459.7619A-100000@ain.charm.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@FreeBSD.org
Precedence: bulk


For some reason at the same time the system decides to not kill any 
processes (except shells) the system won't allow an ls -l of the / 
directory. If one tries /bin/ls /, there is no problem, but for the -long 
information, it just STOPS. In fact very few proceses that do any sort of 
file i/o (cp, find, etc) seem to be working very well. I haven't seen, or 
have reason to believe that the filesystem has errors on it.

Any ideas would be appreciated.