From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 05:15:10 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 DDC8916A4CE for ; Wed, 8 Dec 2004 05:15:10 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72D0743D39 for ; Wed, 8 Dec 2004 05:15:10 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iB85F5mL002416; Wed, 8 Dec 2004 00:15:05 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iB85F52h002413; Wed, 8 Dec 2004 00:15:05 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Wed, 8 Dec 2004 00:15:05 -0500 (EST) From: Andre Guibert de Bruet To: Dan Nelson In-Reply-To: <20041208050620.GG2629@dan.emsphone.com> Message-ID: <20041208000849.D637@alpha.siliconlandmark.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> <20041208050620.GG2629@dan.emsphone.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean 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:15:11 -0000 On Tue, 7 Dec 2004, Dan Nelson wrote: > 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 Noted. I am at a loss to see which of my filesystem it believes is running out of space. /var, the logical choice is not even at 10%: bling# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad4s1a 248M 125M 103M 55% / devfs 1.0K 1.0K 0B 100% /dev procfs 4.0K 4.0K 0B 100% /proc /dev/ad4s1d 248M 14K 228M 0% /tmp /dev/ad4s1e 3.9G 307M 3.3G 8% /var /dev/ad4s1f 180G 6.1G 159G 4% /usr /dev/ad6s1d 180G 20G 145G 12% /mnt/misc /dev/amrd0a 265G 42G 202G 17% /mnt/amrd0a /dev/ad0 226G 111G 97G 53% /mnt/backups devfs 1.0K 1.0K 0B 100% /var/named/dev Thanks! Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ >