From owner-freebsd-current@FreeBSD.ORG Sun Jul 17 12:51:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9BA216A41C for ; Sun, 17 Jul 2005 12:51:22 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D5043D48 for ; Sun, 17 Jul 2005 12:51:22 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 55B1446B3D; Sun, 17 Jul 2005 08:51:22 -0400 (EDT) Date: Sun, 17 Jul 2005 13:51:57 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Nate Lawson In-Reply-To: <42D9D959.5030304@root.org> Message-ID: <20050717135014.E19319@fledge.watson.org> References: <42D9D959.5030304@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current Subject: Re: unnecessary savecore warnings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2005 12:51:23 -0000 On Sat, 16 Jul 2005, Nate Lawson wrote: > I noticed that in the past few months, savecore has begun complaining if > the bounds file in /var/crash doesn't exist. Can we add it to > /usr/src/etc/Makefile like the corresponding entry for minfree? > > Also, I noticed that /etc/rc.d/savecore has started complaining early in > boot if you have dumpdev="AUTO", giving the message "kenv: unable to get > dumpdev". Of course, it works just fine and detects the slice with > "swap" in /etc/fstab. So the warning is spurious and should be > silenced. I've noticed this also, and see if on my NanoBSD Soekris box. Given that the machine doesn't have a partition set up for dumping, and I don't want its dumps, I'd rather it didn't complain, as that will just cause unnecessary worry and questions. This is similar to the devfs-at-shutdown error. An error message that is a result of a harmless "problem" results in significant concern for end-users, which results in more bug reports, less happy users, etc. Robert N M Watson