From owner-freebsd-questions Thu Nov 14 08:19:41 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04646 for questions-outgoing; Thu, 14 Nov 1996 08:19:41 -0800 (PST) Received: from capella.grayphics.com (root@capella.grayphics.com [207.71.216.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04626 for ; Thu, 14 Nov 1996 08:19:34 -0800 (PST) Received: (from nick@localhost) by capella.grayphics.com (8.7.5/8.6.12) id IAA20387; Thu, 14 Nov 1996 08:19:15 -0800 (PST) Date: Thu, 14 Nov 1996 08:19:15 -0800 (PST) From: Nick Esborn To: Frode Nordahl cc: "questions@freebsd.org" Subject: Re: Hackers? In-Reply-To: <199611141447.PAA02691@login.bigblue.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Frode Nordahl wrote: > Can a FreeBSD box do this of itself if it gets into trouble? Memory fault, disk fault or something like that? Or do we have reason > to believe this is hacker activity? FreeBSD will reboot under all critical errors that don't totally lock the machine. In fact, the only time I've ever seen our FBSD machines totally lock was a SCSI bus problem. If that happened to me, I would tend to think it was a fault of some sort, causing the machine to autonamously reboot itself, rather than the act of an intruder. > In any case, what should we do?? If it starts to happen often, you may want to start hardware troubleshooting the machine. If it never happens again, I wouldn't worry about it. Nick Grayphics http://www.grayphics.com/