Date: Fri, 04 Jul 1997 17:15:43 -0600 From: Brett Glass <brett@lariat.org> To: "Gary Palmer" <gpalmer@FreeBSD.ORG> Cc: bugs@FreeBSD.ORG Subject: Re: Serious maintenance bug in 2.2.2-R Message-ID: <3.0.1.32.19970704171543.008f8e00@mail.lariat.org> In-Reply-To: <26265.868052445@orion.webspan.net> References: <Your message of "Fri, 04 Jul 1997 14:49:21 MDT." <3.0.1.32.19970704144921.008e1c40@mail.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I merged the old /etc/crontab with the new, but the line with "newsyslog" was commented out. The documentation states that the "newsyslog" program uses a file called "newsyslog.conf", which was not created during the upgrade. Thus, uncommenting this line will do nothing as it stands. Is a standard "newsyslog.conf" file available? If so, why was it not copied to my system during the upgrade? My real concern is that this could have happened to everyone who did an upgrade. The "class" problem was a minor annoyance; this could cripple a system. --Brett At 05:40 PM 7/4/97 -0400, Gary Palmer wrote: >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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.1.32.19970704171543.008f8e00>