From owner-freebsd-questions@FreeBSD.ORG Fri Jun 4 10:28:56 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A91C16A4F1 for ; Fri, 4 Jun 2004 10:28:56 -0700 (PDT) Received: from ns1.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0447A43D39 for ; Fri, 4 Jun 2004 10:28:55 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from thought.org (tao [10.0.0.247]) by ns1.thought.org (8.12.8p2/8.12.8) with ESMTP id i54HTGRA005346 for ; Fri, 4 Jun 2004 10:29:17 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (localhost [127.0.0.1]) by thought.org (8.12.9p2/8.11.3) with ESMTP id i54HSmmd024011 for ; Fri, 4 Jun 2004 10:28:48 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: (from kline@localhost) by tao.thought.org (8.12.9p2/8.12.11/Submit) id i54HSl8Q023964 for freebsd-questions@FreeBSD.ORG; Fri, 4 Jun 2004 10:28:47 -0700 (PDT) (envelope-from kline) Date: Fri, 4 Jun 2004 10:28:46 -0700 From: Gary Kline To: FreeBSD Mailing List Message-ID: <20040604172846.GA85869@tao.thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing 17 years of service to the Unix community User-Agent: Mutt/1.5.6i Subject: crom output? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 17:28:56 -0000 Here's the latest in the Continuing Adventures of tracking down "why my main server crashes in the wee hours" (usually). I had the memory replaced and am no longer losing tons of file to badly alloc'd index nodes..... *but*, over the weeks that I've ket a /var/log/console.log, tao has usually gone down just after 03:00, when the periodic/daily scripts are run. So: is there any magic-knob I can turn to catch exactly which daily file is causing this? (It may be time to get a newer hard drive, but t hat's another issue.) thanks, people, gary -- Gary Kline kline@thought.org www.thought.org Public service Unix