From owner-freebsd-bugs  Fri Jul  4 14:47:01 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA08725
          for bugs-outgoing; Fri, 4 Jul 1997 14:47:01 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08720
          for <bugs@FreeBSD.ORG>; Fri, 4 Jul 1997 14:46:58 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA23561;
	Fri, 4 Jul 1997 14:48:55 -0700 (PDT)
Message-Id: <199707042148.OAA23561@implode.root.com>
To: Brett Glass <brett@lariat.org>
cc: bugs@FreeBSD.ORG
Subject: Re: Serious maintenance bug in 2.2.2-R 
In-reply-to: Your message of "Fri, 04 Jul 1997 14:49:21 MDT."
             <3.0.1.32.19970704144921.008e1c40@mail.lariat.org> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 04 Jul 1997 14:48:55 -0700
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Upgraded a system to 2.2.2-R not long ago, and just discovered that it was
>running out of disk space. Why? Because the new /etc/daily, /etc/weekly,
>and /etc/monthly no longer cleaned up or rotated the log files! They were
>growing and growing, and began overflowing the disk on this busy system,
>causing all manner of havoc.  Worse still, the nightly backups that
>normally went to our backup catching machine were overflowing ITS disk,
>leaving us vulnerable to data loss.
>
>I don't know whether this problem occurs exclusively on upgrades, but it's
>a ticking time bomb that could cause major problems. Does 2.2.2-R have any
>provisions to rotate and clean up log files? For now, I've added code from
>2.1.0-R to daily.local, weekly.local, and monthly.local to get things back
>under control.

   This is handled by "newsyslog". See /etc/newsyslog.conf and the associated
manual pages.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project