[Fwd: Recent changes to rc.d on -CURRENT]
Mike Makonnen
mtm at identd.net
Tue Jul 27 09:24:58 PDT 2004
On Tue, Jul 27, 2004 at 09:35:33AM -0500, Scot Hetzel wrote:
> On Tue, 27 Jul 2004 13:21:30 +0400, Andrey Chernov <ache at nagual.pp.ru> wrote:
> > On Tue, Jul 27, 2004 at 09:44:39AM +0300, Mike Makonnen wrote:
> > >
> > > The rc.d mechanism with respect to sourcing scripts works like this:
> > > o scripts ending in '.sh' are sourced in the current subshell
> > > o all other scripts are sourced in a subshell.
> >
> > It is unnecessary complication (innovation). Everybody before localpkg
> > using knows he can rename his script to anything excepting ending with
> > ..sh. Say, script.sh.old. Now it is executed. Sigh.
> >
> Only if the script hasn't been converted to rcNG. As rcNG scripts
> require the setting of the <name>_enable="YES" variable in
> /etc/rc.conf, /etc/rc.conf.local, or /etc/rc.conf.d/<name>, before
> they will do any actions.
Yes, that is the way it should be. Non rc.d style scripts *must* have a
'.sh' extension. That doesn't change.
Before anyone mentions it, the
committed version doesn't do that, which is a bug. I'll fix it :-)
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
mtm at identd.net | Fingerprint: AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55
mtm at FreeBSD.Org| FreeBSD - Unleash the Daemon !
More information about the freebsd-ports
mailing list