From owner-freebsd-questions Sat Nov 17 2:32:21 2001 Delivered-To: freebsd-questions@freebsd.org Received: from atkielski.com (atkielski.com [161.58.232.69]) by hub.freebsd.org (Postfix) with ESMTP id BBDCA37B405 for ; Sat, 17 Nov 2001 02:32:19 -0800 (PST) Received: from contactdish (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by atkielski.com (8.11.6) id fAHAWGn78700; Sat, 17 Nov 2001 11:32:17 +0100 (CET) Message-ID: <02a001c16f53$215323b0$0a00000a@atkielski.com> From: "Anthony Atkielski" To: "Kris Kennaway" , "FreeBSD Questions" References: <020e01c16f42$14885c10$0a00000a@atkielski.com> <20011117015632.B87944@xor.obsecurity.org> Subject: Re: Mysterious boot during the night Date: Sat, 17 Nov 2001 11:32:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Agreed, but is there any place in the system where I mind find a clue as to the type of failure encountered? The machine has been running for many days with no failures, mostly churning through SETI@home, so I'd expect fundamental processor problems or incompatibilities to have shown up fairly quickly. My guess would be an intermittent soft failure of some component, i.e., a temporary network anomaly or something that produced a situation leading to a crash, but I'm not sure how to isolate it. Hopefully it will be a once-in-a-lifetime occurrence. ----- Original Message ----- From: "Kris Kennaway" To: "Anthony Atkielski" Cc: "FreeBSD Questions" Sent: Saturday, November 17, 2001 10:56 Subject: Re: Mysterious boot during the night To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message