From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 05:06:22 2004 Return-Path: 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 1174916A4CE for ; Wed, 8 Dec 2004 05:06:22 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEC7843D1D for ; Wed, 8 Dec 2004 05:06:21 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iB856LRo007589; Tue, 7 Dec 2004 23:06:21 -0600 (CST) (envelope-from dan) Date: Tue, 7 Dec 2004 23:06:20 -0600 From: Dan Nelson To: Andre Guibert de Bruet Message-ID: <20041208050620.GG2629@dan.emsphone.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <6.2.0.14.2.20041206114020.08851e60@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041207235104.K637@alpha.siliconlandmark.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 08 Dec 2004 05:06:22 -0000 In the last episode (Dec 07), Andre Guibert de Bruet said: > On Mon, 6 Dec 2004, Manfred Antar wrote: > > >I'm also seeing alot of : > >Dec 6 10:06:53 pozo kernel: Accounting resumed > >Dec 6 10:07:23 pozo kernel: Accounting suspended > >Dec 6 10:07:38 pozo kernel: Accounting resumed > >Dec 6 10:12:23 pozo kernel: Accounting suspended > >Dec 6 10:12:38 pozo kernel: Accounting resumed > >Dec 6 10:12:53 pozo kernel: Accounting suspended > > Ditto. Running accton all by itself to turn off accounting stops > these cycles from occuring (Hardly a fix as you end up without logs > to run reports from). It's a safety device that prevents accounting records from filling up your hard drive in the event of forkbombs, configure scripts or other things that cause high process turnover. It's controlled by the following sysctls: kern.acct_chkfreq: frequency for checking the free space (seconds) kern.acct_resume: percentage of free disk space above which accounting resumes kern.acct_suspend: percentage of free disk space below which accounting stops -- Dan Nelson dnelson@allantgroup.com