From owner-freebsd-questions Tue Nov 20 4:29:33 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 72EF737B405 for ; Tue, 20 Nov 2001 04:29:28 -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 fAKCTNw97769; Tue, 20 Nov 2001 13:29:23 +0100 (CET) Message-ID: <005801c171be$fccc7ff0$0a00000a@atkielski.com> From: "Anthony Atkielski" To: "Jan Grant" Cc: "FreeBSD Questions" References: Subject: Re: Mysterious boot during the night Date: Tue, 20 Nov 2001 13:29:17 +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 Jan writes: > Is this reboot happening nightly at the same time? It has happened only once, so I don't know. On the one occasion when it did happen, it was during the night. I had top running at the time, and the last screen shows processes running that imply that a cron job was running. > There was a cron job running find at the time. Yes. > What filesystem types do you have mounted? Have you > got anything odd (loopback, union, ntfs) there? All default UFS stuff (I just went with what the default installation recommended): freebie# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 992239 90081 822779 10% / /dev/ad0s1f 35433281 2101159 30497460 6% /usr /dev/ad0s1e 694607 4905 634134 1% /var procfs 4 4 0 100% /proc The system is pure FreeBSD, no other boot systems or anything. > Is there a half-formed mail sitting in a queue > somewhere indicating which jobs were running at > the time? In /var/spool/mqueue, you mean? Nope, it's empty. > Can you force a crash manually by going through the > nightly, weekly, monthly periodic jobs? I don't know. The system runs continuously, and cron generates some informative e-mails each night. On the night of the crash, setiathome was running full blast, but it had been doing that on previous nights, too, without a problem. It's mysterious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message