Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles $Revision: 1.7.0.8 $; site uiucdcs Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!inuxc!pur-ee!uiucdcs!acheng From: acheng@uiucdcs.CS.UIUC.EDU Newsgroups: net.unix-wizards Subject: Re: Accounting Suspended out of the blu Message-ID: <13700106@uiucdcs> Date: Mon, 23-Sep-85 12:23:00 EDT Article-I.D.: uiucdcs.13700106 Posted: Mon Sep 23 12:23:00 1985 Date-Received: Tue, 24-Sep-85 23:42:23 EDT References: <127@amc.UUCP> Lines: 24 Nf-ID: #R:amc.UUCP:-12700:uiucdcs:13700106:000:923 Nf-From: uiucdcs.CS.UIUC.EDU!acheng Sep 23 11:23:00 1985 >> This is the 2nd time that our accounting has shut down. The symptoms >> are no accounting (not even for myself :-) and A message >> "Accounting Suspended" printed on the console. > >When the /usr filesystem goes >90% (or is it 95%?) accounting shuts >itself off so that it (rememeber, accounting is done as root, which >doesn't stop writing at 100% full -- it stops at 110%, see the 4.2 filesystem >paper for an explanation) doesn't completely full up the disk. You have >two possible solutions: >... Actually, the kernel suspends accounting writing when the particular filesys is >98% full and resums it only when the filesys is <96% later. That 2% gap will give the adminstrator some time to fiugre out what to do. I usually try to clean up /usr/adm/{wtmp,messages} and /usr/tmp too. albert cheng {ihnp4,pur-ee}!uiucdcs!acheng acheng@UIUC.ARPA acheng@UIUC.CSNET Dept. of Computer Science Univ. of Illinois-Urbana Brought to you by Super Global Mega Corp .com