eric@amc.UUCP (Eric McRae) (09/19/85)
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.
Known facts:
{
VAX 750; 4.2BSD
lastcomm showed nothing unusual completing before the cutoff.
Root was not on the system.
The filesystem that the accounting file was on was 96% full
but there were no complaints about filesystem full near the
cutoff.
Accounting is normally always on.
We clean the accounting files every day.
We are a binary site (yea, both of us :-).
}
Sure would be nice if "accton" put itself into the accounting
file as it shut things down. I know that bypasses the normal
mechanisms but I can wish can't I.
Please respond by email if you have any suggestions.
Eric McRae
Applied Microsystems Corporation
Phys: 5020 148th Ave. N.E. USPS: PO Box C-1002
Redmond, Wa 98052 Redmond, Wa. 98073-1002
UUCP: eric@amc; ..uw-beaver!tikal!amc!eric ATT: (206) 882-2000dave@uwvax.UUCP (Dave Cohrs) (09/21/85)
> 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: 1) delete some stuff -- /usr always has too much junk in it 2) find a larger filesystem for /usr -- Dave Cohrs (608) 262-1204 ...!{harvard,ihnp4,seismo,topaz}!uwvax!dave dave@wisc-romano.arpa