From owner-freebsd-bugs Fri Jul 4 14:40:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08608 for bugs-outgoing; Fri, 4 Jul 1997 14:40:51 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08600 for ; Fri, 4 Jul 1997 14:40:48 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id RAA25829; Fri, 4 Jul 1997 17:40:46 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id RAA26267; Fri, 4 Jul 1997 17:40:46 -0400 (EDT) To: Brett Glass cc: bugs@FreeBSD.ORG From: "Gary Palmer" 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> Date: Fri, 04 Jul 1997 17:40:45 -0400 Message-ID: <26265.868052445@orion.webspan.net> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brett Glass wrote in message ID <3.0.1.32.19970704144921.008e1c40@mail.lariat.org>: > 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. Enable newsyslog in crontab. It works fine here. It seems that you missed out some parts of the upgrade (like merging in a new /etc/crontab) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info