Date: Thu, 16 Jul 2009 10:00:11 +0200 From: Thomas Backman <serenity@exscape.org> To: Alexander Best <alexbestms@math.uni-muenster.de> Cc: freebsd-current@FreeBSD.org Subject: Re: core dumps being overwritten Message-ID: <B18017C3-94E0-4CCC-A632-43A9DFF221A4@exscape.org> In-Reply-To: <permail-2009071607550780e26a0b00006943-a_best01@message-id.uni-muenster.de> References: <permail-2009071607550780e26a0b00006943-a_best01@message-id.uni-muenster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B18017C3-94E0-4CCC-A632-43A9DFF221A4>