From owner-freebsd-current Mon May 27 07:28:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA16757 for current-outgoing; Mon, 27 May 1996 07:28:33 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA16748 for ; Mon, 27 May 1996 07:28:28 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id OAA04000; Mon, 27 May 1996 14:28:21 GMT Date: Mon, 27 May 1996 14:28:21 GMT From: Adam David Message-Id: <199605271428.OAA04000@veda.is> To: freebsd-current@freebsd.org Subject: something's weird with ps X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > toots> ps ax > > > > PID TT STAT TIME COMMAND > > > > 0 ?? DLs 0:00.00 (swapper) > > > > One or more of the set {ps,libkvm,kernel} don't match. > > Nope. (See my previous posting on this). ps/w/libkvm/kernel mismatches > oszillate these days. I wouldn't have asked if it would have been the > 'usual' 'proc size mismatch' error. > > It turned out that it had been a missing /procfs This reminds me, would it be sensible to treat procfs as missing in the case that the proc size mismatches? i.e. print the error, but provide what limited information is available instead of giving up altogether. -- Adam David