From owner-freebsd-current@FreeBSD.ORG  Thu Jul 16 08:00:52 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D25D4106566C
	for <freebsd-current@FreeBSD.org>; Thu, 16 Jul 2009 08:00:52 +0000 (UTC)
	(envelope-from serenity@exscape.org)
Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net
	[80.76.149.212])
	by mx1.freebsd.org (Postfix) with ESMTP id 8C9FA8FC17
	for <freebsd-current@FreeBSD.org>; Thu, 16 Jul 2009 08:00:52 +0000 (UTC)
	(envelope-from serenity@exscape.org)
Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:34352
	helo=mx.exscape.org)
	by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69)
	(envelope-from <serenity@exscape.org>)
	id 1MRLt0-0000Qd-3t; Thu, 16 Jul 2009 10:00:16 +0200
Received: from [192.168.1.5] (macbookpro [192.168.1.5])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by mx.exscape.org (Postfix) with ESMTPSA id 1DD893DA7;
	Thu, 16 Jul 2009 10:00:13 +0200 (CEST)
Message-Id: <B18017C3-94E0-4CCC-A632-43A9DFF221A4@exscape.org>
From: Thomas Backman <serenity@exscape.org>
To: Alexander Best <alexbestms@math.uni-muenster.de>
In-Reply-To: <permail-2009071607550780e26a0b00006943-a_best01@message-id.uni-muenster.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 16 Jul 2009 10:00:11 +0200
References: <permail-2009071607550780e26a0b00006943-a_best01@message-id.uni-muenster.de>
X-Mailer: Apple Mail (2.935.3)
X-Originating-IP: 83.253.252.234
X-Scan-Result: No virus found in message 1MRLt0-0000Qd-3t.
X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MRLt0-0000Qd-3t
	445318a4fa8467fd8b6551a9f1d1e318
Cc: freebsd-current@FreeBSD.org
Subject: Re: core dumps being overwritten
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2009 08:00:53 -0000

On Jul 16, 2009, at 09:55, Alexander Best wrote:

> after a panic and a core dump i was quite surprised to see that one  
> of my
> previous core dumps got overwritten.  is this behaviour controlled  
> by a sysctl
> parameter and has changed recently? i had the following contents in
> /var/crash:
>
> bounds
> core.txt.0
> core.txt.1
> core.txt.2
> info.0
> info.1
> info.2
> minfree
> vmcore.0
> vmcore.1
> vmcore.2
>
> after a panic and core dump core.txt.1, info.1 and vmcore.1 got  
> replaced.
>
> i'm running r195712 (8.0-BETA2).
>
> alex
>
> i'm running r195712.
What does "bounds" contain? savecore reads this file to find the next  
free spot, so to speak. It should contain 3 at this point, but my  
guess is that it says 2, if the previous dump got saved as 1.

Regards,
Thomas