From owner-freebsd-bugs Fri Jul 4 13:49:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA07655 for bugs-outgoing; Fri, 4 Jul 1997 13:49:31 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA07649 for ; Fri, 4 Jul 1997 13:49:28 -0700 (PDT) Received: from anonymous.lariat.org ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id OAA13990 for ; Fri, 4 Jul 1997 14:48:57 -0600 (MDT) Message-Id: <3.0.1.32.19970704144921.008e1c40@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Fri, 04 Jul 1997 14:49:21 -0600 To: bugs@freebsd.org From: Brett Glass Subject: Serious maintenance bug in 2.2.2-R Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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. --Brett Glass