On Tue, Mar 13, 2012 at 11:31:48AM -0300, Daniel Bolgheroni wrote:
> Hi,
> 
> according to rc.conf v1.149, nfs_server was removed and left just as
> backward compatibility.
> 
> However, manpage for rc.conf still refers to nfs_server as an example
> for the second section. FAQ section 6.7 also uses nfs_server instead of
> the newer nfsd_flags.
> 
> Cheers,
> 

hi. note that i'm not addressing the faq issue here.

regarding the man page, rc.conf(5), i have a diff. the current man page
is a bit out of date. i don;t think anyone poking their nose in
/etc/rc.conf will think they are looking at four sections. as time has
gone on, i guess the man page has failed to address the changes being
made.

anyway i've clobbered it a bit. if anyone can see any problems with my
approach, please mail me.

jmc

Index: rc.conf.8
===================================================================
RCS file: /cvs/src/share/man/man8/rc.conf.8,v
retrieving revision 1.19
diff -u -r1.19 rc.conf.8
--- rc.conf.8   8 Jul 2011 17:43:58 -0000       1.19
+++ rc.conf.8   15 Mar 2012 10:07:07 -0000
@@ -51,73 +51,55 @@
 Variables set in this file will override variables previously set in
 .Pa /etc/rc.conf .
 .Pp
-There are four sections in this file.
-The first is used to turn features on or off.
+Some variables are used to turn features on or off.
 For example, whether the system runs the
-.Nm dhcpd
-daemon is determined by the line in this section
+.Xr dhcpd 8
+daemon is determined by the following line:
 .Bd -literal -offset indent
-dhcpd_flags=NO         # for normal use: ""
+dhcpd_flags=NO                 # for normal use: ""
 .Ed
 .Pp
-If this line is edited to contain some valid dhcpd daemon command-line
-flags, such as
+To run the dhcpd daemon,
+add the following line to
+.Nm rc.conf.local :
 .Bd -literal -offset indent
-dhcpd_flags="-A abandoned"     # for normal use: ""
+dhcpd_flags=""                 # for normal use: ""
 .Ed
 .Pp
+If instead some options are specified,
 then the dhcpd daemon will be started with those options.
-.Pp
-The second section contains some other programs that can either be run or not,
-but that don't need options.
-They can be set to YES or NO.
-For example, the line
+For example:
 .Bd -literal -offset indent
-nfs_server=NO
+dhcpd_flags="-A abandoned"     # for normal use: ""
 .Ed
 .Pp
-prevents the NFS server daemons from starting.
-To run NFS, just change this line's value from NO to YES,
-.Sy and
-also make whatever changes are needed for the server
-to have something to do (set up the
-.Xr exports 5
-file etc.).
-.Pp
-The third section contains values that parameterize servers started by
-one of the first two sections, and are ignored if the corresponding
-server is not running.
-For example, if
-.Nm nfs_server ,
-is enabled, then the line
+Other variables specify a simple YES or NO,
+or simply determine the location of a file.
+For example, the location of the ruleset for
+.Xr pf 4
+is given thus:
 .Bd -literal -offset indent
-nfsd_flags="-tun 4"
+pf_rules=/etc/pf.conf           # Packet filter rules file
 .Ed
 .Pp
-provides command-line arguments for the NFS server.
-.Pp
-This particular line instructs
-.Xr nfsd 8
-to start four copies of the server.
-On a busy file server, 8 (or more) copies are recommended.
-.Pp
-The fourth section contains the
+Finally there is the
 .Va pkg_scripts
 variable, responsible for starting and stopping
 .Xr rc.d 8
 scripts installed by packages in the specified order.
-For example, the following line
+For example:
 .Bd -literal -offset indent
 pkg_scripts="dbus_daemon cupsd"
 .Ed
 .Pp
-will run
+This will run
 .Pa /etc/rc.d/dbus_daemon
 then
 .Pa /etc/rc.d/cupsd
 with the
 .Va start
-argument at boot time and in reverse order with the
+argument at boot time,
+and in reverse order with the
 .Va stop
 argument at shutdown.
 .Sh SEE ALSO

Reply via email to