From owner-freebsd-hackers Sat Apr 17 21:21: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id F179A14D0F for ; Sat, 17 Apr 1999 21:21:07 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id AAA23919 for ; Sun, 18 Apr 1999 00:18:43 -0400 (EDT) Message-Id: <199904180418.AAA23919@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: "paused" system Date: Sun, 18 Apr 1999 00:18:42 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have another 'paused' system. It responds to kernel level stuff fine; pings, VTY switches, scroll lock/pgup/pgdn. Nothing beyond that. No network activity beyond what I send at it (the last case had NFS traffic). This is not a critical system this time, so I am quite willing to let it sit for awhile (it seemed to have died on april 15th). Anyone have any commands or anything they would like me to try? BTW: This is a system from the days of 3.1-BETA. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message