From owner-freebsd-questions Wed Jul 5 5:18:43 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.bfm.org (mail.bfm.org [216.127.218.26]) by hub.freebsd.org (Postfix) with ESMTP id 7424B37B993 for ; Wed, 5 Jul 2000 05:18:41 -0700 (PDT) (envelope-from Ryugen@palaver.org) Received: from primo.bfm.org ([216.127.218.20]) by mail.bfm.org (Post.Office MTA v3.5.3 release 223 ID# 0-52399U2500L250S0V35) with SMTP id org for ; Wed, 5 Jul 2000 07:20:09 -0500 Received: from office.palaver.org (unverified [216.176.8.9]) by primo.bfm.org (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 05 Jul 2000 07:18:39 -0500 Message-Id: <4.3.2.7.2.20000705071621.00ad1d40@mail.palaver.org> X-Sender: rfisher@mail.palaver.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 05 Jul 2000 07:18:33 -0500 To: FreeBSD-questions@FreeBSD.ORG From: Ryugen@palaver.org (Ryugen C. Fisher) Subject: ps: bad namelist :addendum Mime-Version: 1.0 Content-Type: text/html; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently upgraded two machines from 3.4 Stable to 3.5 Stable
Both upgrades seemed to go without an problem ---

however:  on the 2nd machine I did, if I enter "ps aux" at the command prompt I get a message back saying "ps: bad namelist"

is this a harbinger of a significant disaster?

does anyone have a clue about what is broke and how to fix it? This is a production machine (the first was a test machine to make sure that there would be no problems on the 2nd.. another theory I need to re-evaluate.....)

In short:  HELP?!

Part Two:

 Went back to the machine in question and ran 'top' for the sake of curiousity.. top produces the following error:

top: nlist failed

In short: HELP?!? still needed.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message