From owner-freebsd-questions Tue Jul 18 18:51:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.monochrome.org (monochrome.org [206.64.112.124]) by hub.freebsd.org (Postfix) with ESMTP id 1ECE537B9C4 for ; Tue, 18 Jul 2000 18:51:18 -0700 (PDT) (envelope-from chris@monochrome.org) Received: from [192.168.1.3] (peche [192.168.1.3]) by mail.monochrome.org (8.9.3/8.9.3) with ESMTP id VAA81898; Tue, 18 Jul 2000 21:50:13 -0400 (EDT) (envelope-from chris@monochrome.org) X-Sender: chris@192.168.1.7 Message-Id: In-Reply-To: <006201bff110$94288f00$84430ace@hacker> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 18 Jul 2000 21:50:14 -0400 To: Michael Lucas , "Josh Paetzel" From: Chris Hill Subject: Re: Overnight lobotomy? Cc: FreeBSD Questions list Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to those who replied. At 7:33 PM -0400 18/7/2000, Josh Paetzel wrote: . . >... a reboot won't hurt anything other than your uptime. True, but I was *this* close to four months :^) (shut down in March to install a sound card). >I know it's a >bold move, but I'd go for it man. If you need some moral support, try the >following phrase, "It's ok to cycle the power when the box is hung." Of course. I was just hoping there might be a possibility of recovering from this, other than just going ahead and Doing the Nasty. Having done it, I'd like to find out *why* it hung, but I'm not sure where to look; the logs are silent on this point. ...and At 11:01 AM -0400 18/7/2000, Michael Lucas wrote: >Check the FreeBSD security advisories; I believe there's a TCP bug >that can damage a 3.3 system. (It definitely affects 3.1). Thanks, I'll take a look. -- Chris Hill chris@monochrome.org [place witty saying here] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message