From freebsd@XtremeDev.com  Tue Oct 24 02:05:56 2000
Return-Path: <freebsd@XtremeDev.com>
Received: from mail.XtremeDev.com (xtremedev.com [216.241.38.65])
	by hub.freebsd.org (Postfix) with ESMTP id 016CD37B479
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 24 Oct 2000 02:05:56 -0700 (PDT)
Received: by mail.XtremeDev.com (Postfix, from userid 1008)
	id CACA05BAD; Tue, 24 Oct 2000 03:05:54 -0600 (MDT)
Message-Id: <20001024090554.CACA05BAD@mail.XtremeDev.com>
Date: Tue, 24 Oct 2000 03:05:54 -0600 (MDT)
From: freebsd@XtremeDev.com
Reply-To: freebsd@XtremeDev.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: /usr/src/UPDATING does not reflect /etc/defaults/rc.conf
X-Send-Pr-Version: 3.2

>Number:         22271
>Category:       conf
>Synopsis:       /usr/src/UPDATING does not reflect /etc/defaults/rc.conf
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    imp
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 24 02:10:03 PDT 2000
>Closed-Date:    Mon Nov 6 12:45:25 MST 2000
>Last-Modified:  Mon Nov 06 12:45:45 MST 2000
>Originator:     FreeBSD
>Release:        FreeBSD 4.1.1-STABLE i386
>Organization:
>Environment:

FreeBSD 4.1.1-STABLE

>Description:

/usr/src/UPDATING has:
20000907:
        Networking defaults have been tightened.  Anybody upgrading
        /etc/defaults/rc.conf needs to add the following lines to
        /etc/rc.conf if they want to have the same setup
        afterwards (unless the variables already are set, of course):
                # Enable network daemons for user convenience.
                inetd_enable="YES"
                portmap_enable="YES"
                sendmail_enable="YES"

And yet /etc/defaults/rc.conf still lists inetd_enable, portmap_enable, and sendmail_enable as "YES". It would appear an MFC never happened, and networking defaults was never "tightened." Should either UPDATING or /etc/defaults/rc.conf be changed before 4.2-RELEASE?

>How-To-Repeat:

A few lines down in /usr/src/UPDATING, and a simple grep of /etc/defaults/rc.conf will confirm.

>Fix:

Either change the relavant lines in /etc/defaults/rc.conf to "NO", or add an entry to /usr/src/UPDATING indicating the network defaults was actually never changed.


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->obrien 
Responsible-Changed-By: johan 
Responsible-Changed-When: Tue Oct 24 12:35:17 PDT 2000 
Responsible-Changed-Why:  
Over to UPDATING maintainer as a reminder to 
remove that entry. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22271 
Responsible-Changed-From-To: obrien->imp 
Responsible-Changed-By: johan 
Responsible-Changed-When: Tue Oct 24 13:17:08 PDT 2000 
Responsible-Changed-Why:  
Ok lets try again. 
Over to UPDATING maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22271 
State-Changed-From-To: open->closed 
State-Changed-By: imp 
State-Changed-When: Mon Nov 6 12:45:25 MST 2000 
State-Changed-Why:  
I just fixed this in the last couple of days. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22271 
>Unformatted:
