Re: init script config files

["Christopher W. Curtis" <ccurtis@aet-usa.com>]

Ethan Benson wrote:
> 
> On Sun, Jul 09, 2000 at 01:22:50AM -0400, Christopher W. Curtis wrote:
> 
> > Because it is not meant to replace ssd, and the additional things that
> > it does do are not proper to be part of ssd as they have nothing to do
> > with starting or stopping daemons.  (eg, status)
> 
> status cannot be done in a generic way, it must be done in each script
> individually, that is the only hope (and a small one at that) of the
> status actually doing anything useful or accurate.

I need to stop using that term.  'consistent exit codes'

> wrong, my implication is that the variables themselves may need to be
> changed, perhaps program arguments change, or perhaps a new default
> should be added.  there are MANY reasons the config file may need to
> be updated.  your implication is that no config file should ever have
> to be upgraded at all, does that apply to say /etc/ssh/sshd_config?

Not at all, simply that a config file change should not incur a
conflict.

> > Using those functions does not meet the definition of obfuscate.
> 
> yes they do.

You have my sympathies.

Christopher