From owner-freebsd-bugs  Sat Oct 21 17:16:21 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id RAA18096
          for bugs-outgoing; Sat, 21 Oct 1995 17:16:21 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA18090
          for <bugs@freebsd.org>; Sat, 21 Oct 1995 17:16:15 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.12/8.6.9) id UAA03517 for bugs@freebsd.org; Sat, 21 Oct 1995 20:20:20 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199510220020.UAA03517@ns1.win.net>
Subject: ps -ax lockup
To: bugs@freebsd.org
Date: Sat, 21 Oct 1995 20:20:20 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 629       
Sender: owner-bugs@freebsd.org
Precedence: bulk


The return of an old friend...heh.

Prior to the 02/10/95 snap I would see a condition where a 'ps' command
would lock up and could not be destroyed.

During the 02/10/95 snap (a very good snap, one of my favorites) the 
problem went away and I haven't seen it until today.  This was on my
main server that is running 2.1-stable with a week lag now from sup.

Just an FYI.  Everything else on the system was functioning correctly.
Web pages, INN, email, sup, all running fine.  Just 'ps' locked up.
"w" and "who" ok.  All pstat options worked.

Regards,

Mark Hittinger
Internet Manager
WinNET Communications, Inc.
bugs@win.net