Date: Fri, 04 Jul 1997 22:39:52 -0400 From: "Gary Palmer" <gpalmer@FreeBSD.ORG> To: Brett Glass <brett@lariat.org> Cc: bugs@FreeBSD.ORG Subject: Re: Serious maintenance bug in 2.2.2-R Message-ID: <25610.868070392@orion.webspan.net> In-Reply-To: Your message of "Fri, 04 Jul 1997 17:15:43 MDT." <3.0.1.32.19970704171543.008f8e00@mail.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Brett Glass wrote in message ID
<3.0.1.32.19970704171543.008f8e00@mail.lariat.org>:
> I merged the old /etc/crontab with the new, but the line with "newsyslog"
> was commented out.
RCS file: /home/ncvs/src/etc/crontab,v
Working file: crontab
head: 1.16
branch:
locks: strict
access list:
symbolic names:
RELENG_2_2_2_RELEASE: 1.13
RELENG_2_2_1_RELEASE: 1.13
RELENG_2_2_0_RELEASE: 1.13
[SNIP]
----------------------------
revision 1.12
date: 1996/01/05 10:09:07; author: graichen; state: Exp; lines: +2 -2
changed /etc/[daily,weekly,monthly] to not rotate the logfiles by
"hand", changed /etc/crontab to call /usr/sbin/newsyslog every hour
(the entry was there before - but we haven't had any newsyslog until
today :-) and changed /etc/inetd.conf to also contain (commentet out)
entries for rpc.rquotad and rpc.sprayd (taken from NetBSD)
----------------------------
root@mutara:/home/src-current/etc> cvs diff -r 1.11 -r 1.12 crontab
Index: crontab
===================================================================
RCS file: /home/ncvs/src/etc/crontab,v
retrieving revision 1.11
retrieving revision 1.12
diff -r1.11 -r1.12
3c3
< # $Id: crontab,v 1.11 1995/11/19 17:21:09 ache Exp $
---
> # $Id: crontab,v 1.12 1996/01/05 10:09:07 graichen Exp $
15c15
< #0 * * * * root /usr/bin/newsyslog
---
> 0 * * * * root /usr/sbin/newsyslog
I think it's uncommented. Certainly is on all newly installed systems
here. The only complaint I've had is that I'd prefer it not to roll
log files over in the middle of the day, but rather at the old
haunting hour of 2am. But thats easily fixed.
> 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?
Depends how you did the upgrade. If you did it with `make world',
there is a stipulation that it CANNOT touch /etc, and if you want the
changes you have to merge them in by hand. If you did it through
sysinstall, then something went wrong and I'm not sure what (You'd
have to ask Jordan)
> 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.
As I said, without knowing just how you did the `upgrade' it's
impossible to say if this is really a problem with the system or not.
Some may argue that `make world' should do what it needs to do, but
I'd really not have it blow away my /etc changes just because someone
touched something.
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?25610.868070392>