From owner-freebsd-arch Thu May 2 14: 7:23 2002 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 031BB37B419; Thu, 2 May 2002 14:07:16 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id CF2215348; Thu, 2 May 2002 23:07:13 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Bill Fenner Cc: jhb@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: savcore dump names? References: <200205021837.LAA21572@windsor.research.att.com> From: Dag-Erling Smorgrav Date: 02 May 2002 23:07:13 +0200 In-Reply-To: <200205021837.LAA21572@windsor.research.att.com> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fenner writes: > - The ability to not save a dump if: > - It would completely fill up the disk (and warn if it would cause disk > usage to go above 100%) > - It would exceed the administrator's configured free space (i.e. > /var/crash/minfree) > - Logging to syslog; errors and messages from the new savecore > are likely to get lost. I liked having things like - Writing sparse files (you think I *enjoy* 640-meg core dumps?) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message