| Summary: | /usr/src/UPDATING does not reflect /etc/defaults/rc.conf | ||
|---|---|---|---|
| Product: | Base System | Reporter: | freebsd <freebsd> |
| Component: | conf | Assignee: | Warner Losh <imp> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.1.1-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-bugs->obrien Over to UPDATING maintainer as a reminder to remove that entry. Responsible Changed From-To: obrien->imp Ok lets try again. Over to UPDATING maintainer. State Changed From-To: open->closed I just fixed this in the last couple of days. |
/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? 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. How-To-Repeat: A few lines down in /usr/src/UPDATING, and a simple grep of /etc/defaults/rc.conf will confirm.