Re: init script config files
Martin Bialasinski wrote:
>
> * "Christopher" == Christopher W Curtis <ccurtis@aet-usa.com> wrote:
>
> Christopher> Every initscript that uses defaults.d (config.d -
> Christopher> whatever) does *not* need to be a conffile. And should
> Christopher> not be. Why? Because anything that can be configurable
>
> Also, I oppose the idea, that part of the scripts in /etc/init.d are
> conffiles and part of them are not. I want consistency and a plain
> simple scheme (the current one is "init scripts are located in
> /etc/init.d and are conffiles. Period.").
That's ok, too. I misspoke when I said they should not be. But they do
not *need* to be. You are correct that what can be done is limited by
what the script provides, but the daemon the script controls is also
limited. If the script is not comprehensive, then yes, there are
definately problems like this.
> Let's look at a init.d file.
>
> # For more exhaustive logging, try "-d 3" as proftpd_options.
> run_proftpd=1
> proftpd_options=""
> [...]
>
> Why would it be easier for the admin to modify these two values in an
> external file instead of the init script? You make this statement, but
> what do you have prove for it?
It is 'easier' because the script maintainer can provide a new version
of the script, perhaps to coincide with a new proftpd that has a new
feature or different syntax, and if the admin makes a change (such as
the -d 3) there is no conflict because the change was made in an
external file, not the script itself.
> Christopher> Either way - if the script uses defaults.d and everything
> Christopher> you need to do can be done from there, there's no need to
> Christopher> modify the initscript.
>
> This ("and everything you need to do can be done from there") is an
> constraint, that I don't see met. You can never say "oh, nobody will
> ever want to change this script".
Well, you could say that if the script supplied doesn't support X
without having to be edited, it should be fixed upstream so that others
can share in the 'fix'. But there's no reason they can't coexist, and
I'm not trying to dictate anything; I'm just showing some code that I
think would make things easier for everyone, and showing how it would be
used. I've not posted any diffs to policy.
regards,
Christopher
Reply to: