[1322] in Release_Engineering
/etc/athena/newsyslog.conf
daemon@ATHENA.MIT.EDU (qjb@ATHENA.MIT.EDU)
Wed Jul 12 08:49:21 1989
From: <qjb@ATHENA.MIT.EDU>
Date: Wed, 12 Jul 89 08:48:48 -0400
To: dkk@ATHENA.MIT.EDU
Cc: rel-eng@ATHENA.MIT.EDU, ops@ATHENA.MIT.EDU, sysdev@ATHENA.MIT.EDU
In-Reply-To: David Krikorian's message of Wed, 12 Jul 89 04:41:31 -0400 <8907120841.AA10346@ALTHEA.MIT.EDU>
Date: Wed, 12 Jul 89 04:41:31 -0400
From: David Krikorian <dkk@ATHENA.MIT.EDU>
Reply-To: dkk@ATHENA.MIT.EDU
Home: 47 Lake St., Arlington, MA 02174, (617) 646-9289
Office: MIT Bldg. E40-358A, (617) 253-8651, 258-8736 (fax)
-------
/site/usr/adm/messages 644 5 30 * Z
/site/usr/spool/mqueue/syslog 644 5 50 * Z
/site/usr/adm/sulog 600 1 10 *
/site/usr/adm/wtmp 644 3 50 * B
/site/usr/adm/findlog 644 1 10 *
/site/usr/adm/lastlog 644 1 20 * B
/site/usr/adm/shutdownlog 644 1 10 *
/site/usr/adm/X0msgs 644 1 10 *
/site/usr/adm/acct 664 1 200 * B
/site/rvd/rvdlog 644 7 * 24
-------
I included /site/usr/adm/acct for those machines with ACCOUNT=true,
and /site/rvd/rvdlog for rvd servers. (The two rvd servers I checked
had rvdlog files of 8200 and 15248 bytes.)
Can anyone think of other logfiles we might have growing out of
control, especially on servers?
I can think of a few more:
/etc/vfsck.log 644 ...
/usr/afs/cores/BosLog 600 ...
I don't know how big these should be or how many. Of course,
vfsck.log must be small as it is on the root (and has to be;
where else can you put fsck's log!).
(/etc/fsck will become vfsck with the next release, right?)
Also, it looks like there's a field missing in /site/rvd/rvdlog.
