From owner-svn-src-head@FreeBSD.ORG Wed Sep 22 21:22:20 2010 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98DB31065673; Wed, 22 Sep 2010 21:22:20 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailB.acsu.buffalo.edu (localmailB.acsu.buffalo.edu [128.205.5.200]) by mx1.freebsd.org (Postfix) with ESMTP id 62C398FC0A; Wed, 22 Sep 2010 21:22:19 +0000 (UTC) Received: from localmailB.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 00F015A47; Wed, 22 Sep 2010 17:15:34 -0400 (EDT) Received: from localmailB.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailB.acsu.buffalo.edu (Postfix) with ESMTP id D2B585A2D; Wed, 22 Sep 2010 17:15:28 -0400 (EDT) Received: from mweb1.acsu.buffalo.edu (mweb1.acsu.buffalo.edu [128.205.5.238]) by localmailB.acsu.buffalo.edu (Prefixe) with ESMTP id BBB0E5966; Wed, 22 Sep 2010 17:15:28 -0400 (EDT) Received: from ken-smiths-macbook-pro.local (cpe-76-180-182-44.buffalo.res.rr.com [76.180.182.44]) by mweb1.acsu.buffalo.edu (Postfix) with ESMTP id 46C945B0038; Wed, 22 Sep 2010 17:15:28 -0400 (EDT) Message-ID: <4C9A71ED.6020406@buffalo.edu> Date: Wed, 22 Sep 2010 17:15:25 -0400 From: Ken Smith User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Andriy Gapon References: <201009211507.o8LF7iVv097676@svn.freebsd.org> <4C9A1602.4020204@freebsd.org> <1285169017.64197.29.camel@buffy.york.ac.uk> <201009221558.27393.jhb@freebsd.org> <4C9A6EE6.5050301@freebsd.org> In-Reply-To: <4C9A6EE6.5050301@freebsd.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-PM-EL-Spam-Prob: XX: 27% Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Gavin Atkinson , src-committers@freebsd.org, John Baldwin Subject: Re: svn commit: r212964 - head/sys/kern X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 21:22:20 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/22/10 5:02 PM, Andriy Gapon wrote: > on 22/09/2010 22:58 John Baldwin said the following: > >> Agreed. FWIW, I actually think that this is the only change needed as >> crashinfo is enabled by default in 8.x and later. We already include symbols >> in kernels by default now, so just setting dumpdev will give you the same >> info you generally can get from a textdump in the form of a simple >> /var/crash/core.txt.N file. >> >> The other benefit of full crashdumps + crashinfo as compared to textdumps is >> that a developer can request further information in a PR followup (fire up >> kgdb and enter command 'X' and reply with the output). With a textdump any >> info not collected by the textdump is lost once the machine reboots after the >> crash. > > Agree++ > But what was the reason that dumpdev="AUTO" was reverted? > I remember that POLA was quoted at the time. > I am not sure what the astonishment actually was - perhaps 'AUTO' was not smart > enough and destroyed somebody's data? > Not everybody would notice /var getting full of crash dumps. Picture a server farm where for the most part the machines are all just plain on auto-pilot. If one or several develop a problem that causes panic's /var can become full and possibly cause the machine to stop doing something important (between panic's...). I wasn't around when the initial decision for what to have it set to was made but this was the reason for me starting to do it again when I realized I forgot to at least once, and hence the reference to POLA. Crash dumps are good for individual workstations. Crash dumps are good for servers *if* the admin knows they're having a problem and is actively working on that server to resolve the issue. But they're no so good and can cause nasty side-effects if they're happening on a machine not being watched over closely. That's the reason for the change in setting when a -stable branch gets started. - -- Ken Smith - - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyace0ACgkQ/G14VSmup/bfKwCdGWyWxuG91GSss6q3MUFAPi2r 6iwAmgLxxEXEODYubhfOFGkzwNx9r/Au =IIBd -----END PGP SIGNATURE-----