Subject: Re: ups-nut rc.d scripts
To: Frederick Bruckman <firstname.lastname@example.org>
From: Johnny Lam <email@example.com>
Date: 11/20/2001 17:16:20
On Tue, Nov 20, 2001 at 04:01:33PM -0600, Frederick Bruckman wrote:
> On Tue, 20 Nov 2001, Johnny Lam wrote:
> > The only downside I see is that pkg.rc.conf will becomes obsolete in 1.6 if
> > we are really switching over to using chkconfig, which is where I think we're
> > headed as chkconfig can be used by tools like sysinst and sushi. At that
> > point, I think we'll want pkgsrc to use chkconfig as well.
> I haven't kept up. What does "chkconfig" do differently? Are there no
> longer defaults in "/etc/defaults/rc.conf"?
It's not built or installed, even in -current, but from my reading of the
implementation in src/sbin/chkconfig, it manages scripts that contain
"chkconfig" as a KEYWORD, and writes files into /etc/rc.conf.d that set
the rc variable to YES or NO. There should still be defaults in
/etc/defaults/rc.conf as that file sourced before sourcing whatever is
in /etc/rc.conf.d. I'm just wondering if at that point, we'll still want
pkgsrc to manage a file in /etc/defaults/pkg.rc.conf when a better way is
forthcoming. Perhaps we should be creating a pkgtools/chkconfig instead?
-- Johnny Lam <firstname.lastname@example.org>