From owner-svn-src-all@FreeBSD.ORG Thu Sep 10 15:37:19 2009 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B6FD106568D; Thu, 10 Sep 2009 15:37:19 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id ABD588FC28; Thu, 10 Sep 2009 15:37:17 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so80173eyf.9 for ; Thu, 10 Sep 2009 08:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=Yeg2iHVA9rDtTmaZmvW+fzoDtbnSDW2j1xj4NYeuJ7U=; b=B49vyiZ+irSXAZS7Ac3yzapMIhqIwnJacwiNTaBDCQfZsbSSo/YhbK9crF2Z+5wOP/ 4FrKHWtfkQNUEf4MOlS3Kt2SBYLqyBlHizM/u8Ic9x4VILQztcexPsr6IpnzUeER/r3R afcMycgOWE+YdAwnQPooIKXw46pkmC1D0s2AA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=vUlFpOGJ6wjMpSFmvisC4SN2PeBIcZIjHNarIAFUFp5TtuC1J2pCnknFO0zh+DoURh 6+Lg3j1tStfUf8mf12VKGxmylFM6JnaZMjN/dk2Ew26tpS4yoSd+tGq5TFM4RE5fiUR1 ZlKk7s2/5CDs9TgoCAK1P58G9KVAUSRugz+Mc= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.7.212 with SMTP id 62mr494977wep.92.1252597036478; Thu, 10 Sep 2009 08:37:16 -0700 (PDT) In-Reply-To: <1252595839.75144.26.camel@bauer.cse.buffalo.edu> References: <200909101404.n8AE41C6021588@svn.freebsd.org> <1252592951.49151.3.camel@buffy.york.ac.uk> <1252595839.75144.26.camel@bauer.cse.buffalo.edu> From: Ivan Voras Date: Thu, 10 Sep 2009 17:36:56 +0200 X-Google-Sender-Auth: 0da9531aab6da75e Message-ID: <9bbcef730909100836l3835825cy83082a2cfe4da0c3@mail.gmail.com> To: Ken Smith Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, src-committers@freebsd.org, svn-src-stable@freebsd.org, svn-src-all@freebsd.org, Gavin Atkinson , svn-src-stable-8@freebsd.org, Ken Smith Subject: Re: svn commit: r197065 - in stable/8: etc/defaults lib/libc/stdlib sys/amd64/conf sys/i386/conf sys/ia64/conf sys/pc98/conf sys/powerpc/conf sys/sparc64/conf X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Sep 2009 15:37:19 -0000 2009/9/10 Ken Smith : > On Thu, 2009-09-10 at 15:29 +0100, Gavin Atkinson wrote: >> This seems like a step backwards to me: crash dumps have been left >> enabled in 7.x and have proved very useful from the point of view of >> improved quality of received PRs. =C2=A0I'm not aware of any problems >> relating to leaving them enabled. >> >> I'd appreciate it if this decision was reconsidered. >> > > Unfortunately as I said before there is no "Right answer" for this one. No, but there is an "80% right" one, based on the question: did the change in 7 cause known problems for any significant number of users (or one of two big users - that should be enough). After all, if users were fine with crashdumps & symbols being enabled in 7, they should be find with them being enabled in 8. > If there is (a lot) more push-back on this we'll reconsider it. But the > AUTO setting is only appropriate for machines that are "actively being > watched over". In -stable branches we start to have people using it for > large data centers full of machines that are only "partially watched > over" at best as well as machines stuffed in phone closets in remote > locations, etc. Having the AUTO setting for situations like that can > mean increased time for a reboot to happen, there is extra risk of the > machine wedging and not rebooting at all (requiring manual intervention > to get it back up), there is risk of disk space issues, etc.