Date: Wed, 13 May 1998 17:43:30 -0700 (PDT) From: toh@finearts.uvic.ca To: freebsd-gnats-submit@FreeBSD.ORG Subject: conf/6629: "upgrade" procedure clobbers /etc/newsyslog.conf in place Message-ID: <199805140043.RAA27868@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 6629 >Category: conf >Synopsis: "upgrade" procedure clobbers /etc/newsyslog.conf in place >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed May 13 17:40:00 PDT 1998 >Last-Modified: >Originator: Marc Sira >Organization: Faculty of Fine Arts, University of Victoria >Release: 2.2.6 >Environment: FreeBSD kenny.finearts.uvic.ca 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Mon May 11 03:31:36 PDT 1998 root@kenny:/usr/src/sys/compile/KENNY i386 >Description: The upgrade procedure (while much nicer than the threatening disclaimer implies :) mistakenly clobbered my /etc/newsyslog.conf file in place, rather than leaving it be and creating a new /etc/upgrade/newsyslog.conf prototype as for the other /etc files. This is so mind-bogglingly minor an issue that I fear divine retribution for even mentioning it, but so be it. >How-To-Repeat: Upgrade from 2.2.5 to 2.2.6 (haven't ever tried upgrade before now, but one imagines it's in the 2.2.6 upgrade procedure, period). >Fix: Just use the same upgrade treatment for newsyslog.conf as all the other little files. :) >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805140043.RAA27868>