Subject: re: CVS commit: basesrc/etc/rc.conf.d
To: Darren Reed <email@example.com>
From: matthew green <firstname.lastname@example.org>
Date: 04/19/2002 00:26:49
In some email I received from Perry E. Metzger, sie wrote:
> Well, of course -- the directory is created (empty) by mtree(8). There
> wasn't any need for files to initialize it from because it was
> supposed to be used only by the end user. (I think we're all in
> complete agreement here except for Darren.)
why would an end user want to create & use that file when they can
just edit rc.conf ?
so that i can do this:
# echo command=/usr/pkg/sbin/named > /etc/rc.conf.d/named
and then "/etc/rc.d/named start" will use the named in pkgsrc.
this feature has proven to be extremely useful.
i also know you've seen an example rc.conf.d/sshd that was
so that a 3rd party package can install an rc.d script and a
configuration file for it, that is easy to remove. this was
actually a requirement of rc.d.