From owner-freebsd-questions@FreeBSD.ORG Thu Mar 8 22:56:57 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01D951065670 for ; Thu, 8 Mar 2012 22:56:57 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id A59858FC16 for ; Thu, 8 Mar 2012 22:56:56 +0000 (UTC) Received: from mail.unitedinsong.com.au (bell.herveybayaustralia.com.au [192.168.0.40]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 6CBE55C2B for ; Fri, 9 Mar 2012 09:10:26 +1000 (EST) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.177]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id DA3C15C22 for ; Fri, 9 Mar 2012 09:10:25 +1000 (EST) Message-ID: <4F593800.2090001@herveybayaustralia.com.au> Date: Fri, 09 Mar 2012 08:51:44 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Capturing Information About PANIC X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2012 22:56:57 -0000 On 03/09/12 01:45, Dean E. Weimer wrote: > I am having problems with my system panicking and crashing during > Bacula backups. Is there any way short of enabling full memory dumps > to log the output of the crash? After a reboot there is no > information in the messages log, and dmesg generally only shows the > information since the reboot started. You can enable all.log in syslog.conf (follow the instructions there); this will provide verbose logging of everything at all levels. And you can enable dumpdev in rc.conf. HTH