Re: enable/disable flags in /etc/default
]] Bastian Blywis
| > The use case for this is:
| > - install daemon
| > - install configuration using puppet/chef/cfengine/etc
| > - start daemon or hook daemon into tool that keeps it running (monit,
| > god, etc)
| Is there any reason against using a debconf script that asks if the
| daemon should be started at boot time (or on which runlevels)? That
| way you can easily modify the configuration with dpkg-reconfigure and
| benefit from the debconf frontends.
If you use a configuration management framework you probably don't care
that much about debconf, since the debconfiscation of packages is fairly
spotty and doesn't really lend itself to more complex setup.
Imagine having a full nagios or munin configuration done through debconf
and then imagine the preseed needed for that. Compare that with just
dumping a configuration file somewhere. Also, consider that a
configuration file might be generated based on what hosts exist in your
infrastructure, which would mean that all debconf use would gain you is
you'd have to generate the preseed file and reconfigure packages on
changes. At that point, you haven't really won anything.
Hooking update-rc.d into debconf is probably not the worst idea in the
world, except update-rc.d is supposed to be run non-interactively and I
think it's the wrong place in the stack to configure that functionaliy.
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are